LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ivan Babrou <ivan@cloudflare.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: Linux 4.19 and GCC 9
Date: Fri, 17 May 2019 13:52:16 +0200 [thread overview]
Message-ID: <20190517115216.GB662@kroah.com> (raw)
In-Reply-To: <20190517094217.GA13913@kroah.com>
On Fri, May 17, 2019 at 11:42:17AM +0200, Greg KH wrote:
> On Fri, May 17, 2019 at 11:27:41AM +0200, Miguel Ojeda wrote:
> > On Fri, May 17, 2019 at 11:23 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> > >
> > > > a6e60d84989f ("include/linux/module.h: copy __init/__exit attrs to
> > > > init/cleanup_module")
> > >
> > > That patch I applied now.
> >
> > Note that this one requires the second one (c0d9782f5b6d).
>
> Oops, yeah, my build boxes just blew up :)
>
> Let me go take the time to do this correctly now...
Ugh, that is a mess. I'm going to leave this alone for now as I have
other things to work on.
If someone wants to send a properly backported set of patches, for
4.19.y and older, that would be wonderful :)
Otherwise this is going to have to wait for a while...
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-17 11:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABWYdi06NUOWRLingNuybgZZsTZPjhmsOx-9oCGK94qZGYbzcw@mail.gmail.com>
[not found] ` <CANiq72kvpiC-i53AXM-YsCUvWroHQemmqxsXjnB330ZEeHahUg@mail.gmail.com>
[not found] ` <CABWYdi1zhTTaN-GSgH0DnPfz7p=SRw0wts5QVYYVtfvoiS0qnQ@mail.gmail.com>
2019-05-16 21:20 ` Miguel Ojeda
2019-05-16 21:24 ` Ivan Babrou
2019-05-17 2:03 ` Josh Poimboeuf
2019-05-17 3:14 ` Ivan Babrou
2019-05-17 5:09 ` Greg KH
2019-05-17 7:38 ` Peter Zijlstra
2019-05-17 8:35 ` Miguel Ojeda
2019-05-17 8:51 ` Greg KH
2019-05-17 9:01 ` Miguel Ojeda
2019-05-17 9:23 ` Greg KH
2019-05-17 9:27 ` Miguel Ojeda
2019-05-17 9:42 ` Greg KH
2019-05-17 11:52 ` Greg KH [this message]
2019-05-17 9:48 ` Greg KH
2019-05-17 15:22 ` Arnaldo Carvalho de Melo
2019-05-17 17:23 ` Ivan Babrou
2019-05-17 17:37 ` Arnaldo Carvalho de Melo
2019-06-10 7:21 ` Ivan Babrou
2019-06-10 7:45 ` Greg KH
2019-06-10 9:32 ` Ignat Korchagin
2019-06-10 14:21 ` Greg KH
2019-06-10 14:42 ` Miguel Ojeda
2019-06-10 14:48 ` Greg KH
2019-06-10 15:01 ` Ignat Korchagin
2019-06-10 15:04 ` Miguel Ojeda
2019-06-10 15:14 ` Arnaldo Carvalho de Melo
2019-06-10 15:25 ` Greg KH
2019-06-10 19:14 ` Arnaldo Carvalho de Melo
2019-06-24 10:42 ` Ignat Korchagin
2019-06-25 7:50 ` Greg KH
2019-06-25 8:08 ` Greg KH
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=20190517115216.GB662@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ivan@cloudflare.com \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--subject='Re: Linux 4.19 and GCC 9' \
/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
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).