From: Greg KH <gregkh@linuxfoundation.org>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4.20 000/111] 4.20.4-stable review
Date: Mon, 21 Jan 2019 16:10:20 +0100 [thread overview]
Message-ID: <20190121151020.GB4717@kroah.com> (raw)
In-Reply-To: <CAA85sZum33M+1NRcfWkua+66CBTxM8ope+hoGASv6mR8NrwPTg@mail.gmail.com>
On Mon, Jan 21, 2019 at 03:56:24PM +0100, Ian Kumlien wrote:
> On Mon, Jan 21, 2019 at 3:47 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Jan 21, 2019 at 03:44:24PM +0100, Ian Kumlien wrote:
> > > Hi,
> > >
> > > IMHO you are missing: 41d1c8839e5f8cb781cc635f12791decee8271b7
> > >
> > > Which should be marked for stable, it fixes:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=202235
> >
> > The networking maintainer handles sending those patches to me. It
> > wasn't part of the last set of patches, so perhaps it will be in the
> > next one?
>
> I thought it would be in the next one after it's in the rc but perhaps not...
>
> I suspected that it could have been a slip up, since:
> https://marc.info/?l=linux-netdev&m=154726015506044&w=2
>
> And i know that there are people waiting for it ;)
Well, ask David and if he says I can queue it up now, I'll be glad to do
so.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-21 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 14:44 Ian Kumlien
2019-01-21 14:46 ` Greg KH
2019-01-21 14:56 ` Ian Kumlien
2019-01-21 15:10 ` Greg KH [this message]
2019-01-21 15:38 ` Ian Kumlien
2019-01-21 18:48 ` David Miller
2019-01-21 19:21 ` Greg KH
2019-01-21 19:43 ` David Miller
2019-01-21 19:27 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2019-01-21 13:41 Greg Kroah-Hartman
2019-01-22 13:33 ` Naresh Kamboju
2019-01-22 16:44 ` Greg Kroah-Hartman
2019-01-22 19:24 ` Guenter Roeck
2019-01-23 6:43 ` Greg Kroah-Hartman
2019-01-22 22:25 ` shuah
2019-01-23 6:43 ` Greg Kroah-Hartman
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=20190121151020.GB4717@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ian.kumlien@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome