From: Paul Burton <paul.burton@mips.com>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH v4 3/7] mips: rename macros and files from '64' to 'n64'
Date: Thu, 13 Dec 2018 20:15:41 +0000 [thread overview]
Message-ID: <20181213201540.ae6pxtm2xmrxnaaa@pburton-laptop> (raw)
In-Reply-To: <CALxhOnht8H6r38bwm7xqbHuJs6dvLB03GCKyws2cif1mEE+sKA@mail.gmail.com>
Hi Firoz,
On Thu, Dec 13, 2018 at 02:23:21PM +0530, Firoz Khan wrote:
> > > So If you confirm I can send v5 without '64' to 'n64' conversion (not just above
> > > one, completely from this patch series). Or uou can take a call just
> > > keep this macro -
> > > _MIPS_SIM_ABI64 as it is and change it rest of the place.
> >
> > Let's just go ahead & leave everything as 64, and I'll do the 64 -> n64
> > rename later. I hoped whilst you were adding n64-specific code this
> > would be an easy change, but at this point let's just prioritize getting
> > the series applied without the naming change so it can sit in -next for
> > a while before the merge window.
>
> I'll keep the macro - _MIPS_SIM_ABI64 same and will not change the rest
> of the patch series. Unfortunately, reverting back to 64 from n64 has lots of
> work.
I've applied v5 but undone the change from __NR_64_* to __NR_N64_*
because it's part of the UAPI & a github code search showed that it's
actually used.
Could you take a look at this branch & check that you're OK with it
before I push it to mips-next?
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git test-syscalls
https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/log/?h=test-syscalls
Thanks,
Paul
next prev parent reply other threads:[~2018-12-13 20:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 5:18 [PATCH v4 0/7] mips: system call table generation support Firoz Khan
2018-12-06 5:18 ` [PATCH v4 1/7] mips: add __NR_syscalls along with __NR_Linux_syscalls Firoz Khan
2018-12-06 5:18 ` [PATCH v4 2/7] mips: remove unused macros Firoz Khan
2018-12-06 5:18 ` [PATCH v4 3/7] mips: rename macros and files from '64' to 'n64' Firoz Khan
2018-12-10 19:51 ` Paul Burton
2018-12-10 23:32 ` Maciej W. Rozycki
2018-12-10 23:46 ` Paul Burton
2018-12-11 10:58 ` Maciej W. Rozycki
2018-12-11 8:45 ` Firoz Khan
2018-12-11 18:59 ` Paul Burton
2018-12-12 4:34 ` Firoz Khan
2018-12-12 22:28 ` Paul Burton
2018-12-13 8:53 ` Firoz Khan
2018-12-13 20:15 ` Paul Burton [this message]
2018-12-14 5:50 ` Firoz Khan
2018-12-06 5:18 ` [PATCH v4 4/7] mips: add +1 to __NR_syscalls in uapi header Firoz Khan
2018-12-06 5:18 ` [PATCH v4 5/7] mips: remove syscall table entries Firoz Khan
2018-12-06 5:18 ` [PATCH v4 6/7] mips: add system call table generation support Firoz Khan
2018-12-06 5:18 ` [PATCH v4 7/7] mips: generate uapi header and system call table files Firoz Khan
2018-12-10 5:35 ` [PATCH v4 0/7] mips: system call table generation support Firoz Khan
2018-12-10 5:41 ` Paul Burton
2018-12-10 8:05 ` Firoz Khan
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=20181213201540.ae6pxtm2xmrxnaaa@pburton-laptop \
--to=paul.burton@mips.com \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhogan@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.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
all inboxes | Powered by JetHome®