From: Zack Weinberg <zackw@panix.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4 1/8] sysv/linux: Rename alpha functions to be alpha specific
Date: Fri, 28 Feb 2020 12:52:45 -0500 [thread overview]
Message-ID: <CAKCAbMgZDvSwwf8p2LWJi3hXp28aF1Oek=Kxk+xd6_DuZ3HqHA@mail.gmail.com> (raw)
In-Reply-To: <f1d9de38-d24c-6694-15b3-3633132209a2@linaro.org>
On Fri, Feb 28, 2020 at 12:30 PM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> On 19/02/2020 15:10, Alistair Francis wrote:
> > These functions are alpha specifc, rename them to be clear.
> >
> > Let's also rename the header file from tv32-compat.h to
> > alpha-tv32-compat.h. This is to avoid conflicts with the one we will
> > introduce later.
> >
> > Reviewed-by: Lukasz Majewski <lukma@denx.de>
>
> My understanding is Zack has raise a strong objetion with this patch.
> I would also like to make this patch move forward, so Zack do you
> still have objections about this? If so, what do you propose instead?
I want alpha to use the same tv32-compat.h as all the other
architectures that need these conversions. I thought the previous
round of discussion had come up with a plan to make that happen, so
I'm surprised to see it hasn't. What happened there?
zw
next prev parent reply other threads:[~2020-02-28 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:10 [PATCH v4 0/8] Always use 32-bit time_t for certain syscalls Alistair Francis
2020-02-19 18:10 ` [PATCH v4 1/8] sysv/linux: Rename alpha functions to be alpha specific Alistair Francis
2020-02-28 17:30 ` Adhemerval Zanella
2020-02-28 17:52 ` Zack Weinberg [this message]
2020-02-19 18:10 ` [PATCH v4 2/8] time: Add a timeval with a 32-bit tv_sec and tv_usec Alistair Francis
2020-02-19 18:10 ` [PATCH v4 3/8] time: Add a __itimerval64 struct Alistair Francis
2020-02-19 18:10 ` [PATCH v4 4/8] sysv: Define __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64 Alistair Francis
2020-02-19 18:10 ` [PATCH v4 5/8] linux: Use long time_t __getitimer/__setitimer Alistair Francis
2020-02-21 10:03 ` Lukasz Majewski
2020-02-28 16:56 ` Lukasz Majewski
2020-02-19 18:10 ` [PATCH v4 6/8] resource: Add a __rusage64 struct Alistair Francis
2020-02-19 18:10 ` [PATCH v4 7/8] linux: Use long time_t for wait4/getrusage Alistair Francis
2020-02-21 10:08 ` Lukasz Majewski
2020-02-19 18:10 ` [PATCH v4 8/8] sysv/alpha: Use generic __timeval32 and helpers Alistair Francis
2020-02-21 9:52 ` Lukasz Majewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKCAbMgZDvSwwf8p2LWJi3hXp28aF1Oek=Kxk+xd6_DuZ3HqHA@mail.gmail.com' \
--to=zackw@panix.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).