From: Alistair Francis <alistair23@gmail.com>
To: Zack Weinberg <zackw@panix.com>
Cc: Lukasz Majewski <lukma@denx.de>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH v5 1/8] sysv/linux: Rename alpha functions to be alpha specific
Date: Mon, 9 Mar 2020 15:16:48 -0700 [thread overview]
Message-ID: <CAKmqyKPu7er9dfUkfFe4WUyGoCzRy9Juq2tqY3JvPbLyU+6G7g@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMgoOtHjx-Tg0+x9zOynCFnzgfjrK8Zf6OqVpvt0MPvZ4g@mail.gmail.com>
On Thu, Mar 5, 2020 at 1:38 PM Zack Weinberg <zackw@panix.com> wrote:
>
> On Thu, Mar 5, 2020 at 4:51 AM Lukasz Majewski <lukma@denx.de> 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.
> >
> > Are there any more comments for this patch set from Alistair? Is it
> > eligible for pulling?
>
> I don't have time to go over the whole patch set in detail this week,
> but I see that it ends up removing alpha-tv32-compat.h by the end of
> the series, so the specific concerns I had with earlier iterations
> seem to be addressed.
Ping!
Am I ok to push this series? It's been reviewed and tested by Lukasz
and no one else seems to have any complaints.
Alistair
>
> zw
next prev parent reply other threads:[~2020-03-09 22:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 18:01 [PATCH v5 0/8] Always use 32-bit time_t for certain syscalls Alistair Francis
2020-03-03 18:01 ` [PATCH v5 1/8] sysv/linux: Rename alpha functions to be alpha specific Alistair Francis
2020-03-05 9:51 ` Lukasz Majewski
2020-03-05 21:38 ` Zack Weinberg
2020-03-09 22:16 ` Alistair Francis [this message]
2020-03-12 18:45 ` Alistair Francis
2020-03-18 19:46 ` Alistair Francis
2020-03-24 7:33 ` Lukasz Majewski
2020-03-24 23:58 ` Alistair Francis
2020-03-27 16:15 ` Adhemerval Zanella
2020-03-27 16:25 ` Alistair Francis
2020-03-27 16:46 ` Adhemerval Zanella
2020-03-03 18:01 ` [PATCH v5 5/8] linux: Use long time_t __getitimer/__setitimer Alistair Francis
2020-03-27 18:09 ` Adhemerval Zanella
2020-03-27 18:21 ` Alistair Francis
2020-03-03 18:01 ` [PATCH v5 7/8] linux: Use long time_t for wait4/getrusage Alistair Francis
2020-03-27 18:31 ` Adhemerval Zanella
2020-03-27 18:42 ` Alistair Francis
2020-04-04 14:52 ` Andreas Schwab
2020-03-03 18:01 ` [PATCH v5 6/8] resource: Add a __rusage64 struct Alistair Francis
2020-03-27 18:14 ` Adhemerval Zanella
2020-03-03 18:01 ` [PATCH v5 2/8] time: Add a timeval with a 32-bit tv_sec and tv_usec Alistair Francis
2020-03-27 17:00 ` Adhemerval Zanella
2020-03-03 18:01 ` [PATCH v5 8/8] sysv/alpha: Use generic __timeval32 and helpers Alistair Francis
2020-04-01 16:57 ` Adhemerval Zanella
2020-04-01 16:54 ` Alistair Francis
2020-03-03 18:01 ` [PATCH v5 4/8] sysv: Define __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64 Alistair Francis
2020-03-27 17:58 ` Adhemerval Zanella
2020-03-27 18:36 ` Alistair Francis
2020-03-03 18:01 ` [PATCH v5 3/8] time: Add a __itimerval64 struct Alistair Francis
2020-03-27 17:01 ` Adhemerval Zanella
2020-04-04 13:58 ` [PATCH v5 0/8] Always use 32-bit time_t for certain syscalls Andreas Schwab
2020-04-06 13:24 ` Adhemerval Zanella
2020-04-06 14:03 ` Andreas Schwab
2020-04-06 16:16 ` Adhemerval Zanella
2020-04-06 17:07 ` Andreas Schwab
2020-04-06 17:34 ` Adhemerval Zanella
2020-04-06 17:43 ` Adhemerval Zanella
2020-04-06 17:48 ` Andreas Schwab
2020-04-06 17:45 ` Alistair Francis
2020-04-06 18:02 ` Alistair Francis
2020-04-06 18:21 ` Adhemerval Zanella
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKmqyKPu7er9dfUkfFe4WUyGoCzRy9Juq2tqY3JvPbLyU+6G7g@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=lukma@denx.de \
--cc=zackw@panix.com \
/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).