From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: firoz.khan@linaro.org, Linux-sh list <linux-sh@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Greg KH <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@linaro.org
Subject: Re: [PATCH v3 0/3] sh: system call table generation support
Date: Mon, 19 Nov 2018 02:57:59 -0600 [thread overview]
Message-ID: <72faac80-114f-f563-b340-0cdeea2673cd@landley.net> (raw)
In-Reply-To: <CAMuHMdUKPo6Lu0CtWERYkQTKSATqq0QVit-Awcn1O2EsS22iKQ@mail.gmail.com>
On 11/19/18 2:08 AM, Geert Uytterhoeven wrote:
> On Mon, Nov 19, 2018 at 6:26 AM Rob Landley <rob@landley.net> wrote:
>> WARNING: CPU: 0 PID: 1 at mm/slub.c:2448 ___slab_alloc.constprop.34+0x196/0x288
>
> https://patchwork.kernel.org/patch/10549883/
Given that Sato-san is co-maintainer of arch/sh and that was posted in July, why
is it not upstream yet?
Rob
prev parent reply other threads:[~2018-11-19 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 4:32 [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 1/3] sh: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-11-19 16:50 ` Arnd Bergmann
2018-11-20 7:05 ` Firoz Khan
2018-11-14 4:32 ` [PATCH v3 2/3] sh: add system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 3/3] sh: generate uapi header and syscall table header files Firoz Khan
2018-11-19 5:08 ` [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-12-10 20:30 ` Rich Felker
2018-11-19 5:25 ` Rob Landley
2018-11-19 8:08 ` Geert Uytterhoeven
2018-11-19 8:57 ` Rob Landley [this message]
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=72faac80-114f-f563-b340-0cdeea2673cd@landley.net \
--to=rob@landley.net \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
--cc=ysato@users.sourceforge.jp \
/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).