From: Firoz Khan <firoz.khan@linaro.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>, Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ram Pai <linuxram@us.ibm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Boqun Feng <boqun.feng@gmail.com>,
Breno Leitao <leitao@debian.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Deepa Dinamani <deepa.kernel@gmail.com>
Subject: Re: [PATCH v5 0/5] powerpc: system call table generation support
Date: Mon, 17 Dec 2018 16:12:37 +0530 [thread overview]
Message-ID: <CALxhOnh5a86pBi4rD1YzhVGq7KPs56du9+G8vkt7zVAqbGkLEw@mail.gmail.com> (raw)
Message-ID: <20181217104237.qVERWcf0_975LpU8gEibxsriFTdGvpMRgC7eIdxGDs8@z> (raw)
In-Reply-To: <877eg8v40t.fsf@concordia.ellerman.id.au>
Hi Michael,
On Mon, 17 Dec 2018 at 16:01, Michael Ellerman <mpe@ellerman.id.au> wrote:
> No it's fine if it applies on next.
>
> I can also fix up minor merge conflicts if there are any.
Ohh. I already rebased and sent v6.
Thanks
Firoz
next prev parent reply other threads:[~2018-12-17 10:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 9:02 [PATCH v5 0/5] powerpc: system call table generation support Firoz Khan
2018-12-13 9:02 ` Firoz Khan
2018-12-13 9:02 ` [PATCH v5 1/5] powerpc: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-12-13 9:02 ` Firoz Khan
2018-12-13 9:02 ` [PATCH v5 2/5] powerpc: move macro definition from asm/systbl.h Firoz Khan
2018-12-13 9:02 ` Firoz Khan
2018-12-13 9:02 ` [PATCH v5 3/5] powerpc: add system call table generation support Firoz Khan
2018-12-13 9:02 ` Firoz Khan
2018-12-13 9:02 ` [PATCH v5 4/5] powerpc: split compat syscall table out from native table Firoz Khan
2018-12-13 9:02 ` Firoz Khan
2018-12-13 9:02 ` [PATCH v5 5/5] powerpc: generate uapi header and system call table files Firoz Khan
2018-12-13 9:02 ` Firoz Khan
2018-12-17 8:08 ` [PATCH v5 0/5] powerpc: system call table generation support Satheesh Rajendran
2018-12-17 8:08 ` Satheesh Rajendran
2018-12-17 9:43 ` Firoz Khan
2018-12-17 9:43 ` Firoz Khan
2018-12-17 10:30 ` Michael Ellerman
2018-12-17 10:30 ` Michael Ellerman
2018-12-17 10:42 ` Firoz Khan [this message]
2018-12-17 10:42 ` Firoz Khan
2018-12-17 13:06 ` Michael Ellerman
2018-12-17 13:06 ` Michael Ellerman
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=CALxhOnh5a86pBi4rD1YzhVGq7KPs56du9+G8vkt7zVAqbGkLEw@mail.gmail.com \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=deepa.kernel@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=leitao@debian.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pombredanne@nexb.com \
--cc=sathnaga@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).