From: Greg KH <gregkh@linuxfoundation.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: stable@vger.kernel.org
Subject: Re: nfp: don't tell FW about the reserved buffer space
Date: Sun, 1 Jul 2018 18:05:10 +0200 [thread overview]
Message-ID: <20180701160510.GA24643@kroah.com> (raw)
In-Reply-To: <20180701144953.GB1332@kroah.com>
On Sun, Jul 01, 2018 at 04:49:54PM +0200, Greg KH wrote:
> On Fri, Jun 29, 2018 at 02:03:48PM -0700, Jakub Kicinski wrote:
> > Hi!
> >
> > Can we get the following backported to the 4.9 branch?
> >
> > commit 9383b33771e566fa547daa2d09c6e0f1aaa298c3
> > Author: Jakub Kicinski <jakub.kicinski@netronome.com>
> > Date: Thu Mar 2 15:26:20 2017 -0800
>
> Now applied, thanks.
And it breaks the build :(
Please provide a working patch if you want it in the stable release.
And always test these before asking. Having patches break a build is
very annoying...
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-01 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 21:03 nfp: don't tell FW about the reserved buffer space Jakub Kicinski
2018-07-01 14:49 ` Greg KH
2018-07-01 16:05 ` Greg KH [this message]
2018-07-02 5:32 ` Jakub Kicinski
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=20180701160510.GA24643@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jakub.kicinski@netronome.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).