From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, arnd@arndb.de
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings from the build of Linus' tree
Date: Thu, 11 Oct 2018 09:44:36 +0200 [thread overview]
Message-ID: <d5b166d6-461c-f382-e3d2-8993b845bd5a@linux.ibm.com> (raw)
In-Reply-To: <20181011114809.5590ecb3@canb.auug.org.au>
On 11.10.2018 02:48, Stephen Rothwell wrote:
> OK, I have been carrying this "quick fix" patch in linux-next since
> September 7. Is anyone going to pick this up and send it to
> Greg/Linus, please?
Sorry about that - I posted a modified fix at
https://lkml.org/lkml/2018/9/13/367
but didn't get a response. I guess I should have reposted sooner. But
before I do that:
Arnd: Is this something that you can pick up or should I include someone
else?
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
next prev parent reply other threads:[~2018-10-11 7:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 3:32 linux-next: build warnings from the build of Linus' tree Stephen Rothwell
2018-08-24 8:20 ` Masami Hiramatsu
2018-08-24 11:47 ` Masami Hiramatsu
2018-08-24 12:42 ` Stephen Rothwell
2018-08-25 1:51 ` Masami Hiramatsu
2018-08-26 8:10 ` Masami Hiramatsu
2018-08-27 21:23 ` Stephen Rothwell
2018-08-28 0:43 ` Masami Hiramatsu
2018-09-06 10:49 ` Peter Oberparleiter
2018-09-06 16:42 ` Masami Hiramatsu
2018-09-07 12:50 ` Peter Oberparleiter
2018-09-08 3:57 ` Masami Hiramatsu
2018-09-10 13:27 ` Peter Oberparleiter
2018-09-11 11:49 ` Masami Hiramatsu
2018-09-11 14:10 ` Masami Hiramatsu
2018-09-06 22:14 ` Stephen Rothwell
2018-09-07 3:34 ` Stephen Rothwell
2018-10-11 0:48 ` Stephen Rothwell
2018-10-11 7:44 ` Peter Oberparleiter [this message]
2018-10-11 9:58 ` Stephen Rothwell
2018-10-11 10:37 ` Greg KH
2018-10-11 11:09 ` Peter Oberparleiter
2018-10-11 13:54 ` Arnd Bergmann
2018-10-11 22:12 ` [GIT PULL] A couple of warning fixes Stephen Rothwell
2018-10-12 10:51 ` Greg KH
2018-08-24 12:46 ` linux-next: build warnings from the build of Linus' tree Arnd Bergmann
2018-08-25 18:53 ` Masami Hiramatsu
2018-08-25 19:53 ` Arnd Bergmann
2018-09-01 9:50 ` Masami Hiramatsu
2018-09-01 12:38 ` [PATCH] ARM: linker script: GCOV kernel may refers data in __exit Masami Hiramatsu
2018-09-11 14:12 ` Masami Hiramatsu
2018-08-29 2:11 ` linux-next: build warnings from the build of Linus' tree Greentime Hu
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=d5b166d6-461c-f382-e3d2-8993b845bd5a@linux.ibm.com \
--to=oberpar@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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).