From: David Miller <davem@davemloft.net>
To: simon.horman@netronome.com
Cc: jakub.kicinski@netronome.com, netdev@vger.kernel.org,
oss-drivers@netronome.com
Subject: Re: [PATCH net repost] nfp: do not update MTU from BH in flower app
Date: Tue, 15 Aug 2017 21:03:58 -0700 (PDT) [thread overview]
Message-ID: <20170815.210358.1704629747295212922.davem@davemloft.net> (raw)
In-Reply-To: <20170815.175240.1812725528326133547.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Tue, 15 Aug 2017 17:52:40 -0700 (PDT)
> From: Simon Horman <simon.horman@netronome.com>
> Date: Tue, 15 Aug 2017 08:13:48 +0200
>
>> Could you pull net into net-next? I'd like to send up a follow-up
>> for net-next to allow processing of the MTU.
>
> Once Linus takes the pull request I just sent to him, I will
> do this.
And this is now done.
next prev parent reply other threads:[~2017-08-16 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 8:18 [PATCH net repost] nfp: do not update MTU from BH in flower app Simon Horman
2017-08-11 21:51 ` David Miller
2017-08-15 6:13 ` Simon Horman
2017-08-16 0:52 ` David Miller
2017-08-16 4:03 ` David Miller [this message]
2017-08-16 5:35 ` Simon Horman
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=20170815.210358.1704629747295212922.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.com \
/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).