From: Jakub Kicinski <kuba@kernel.org>
To: Shenwei Wang <shenwei.wang@nxp.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: Re: [EXT] Re: [PATCH v2 0/2] net: fec: optimization and statistics
Date: Tue, 8 Nov 2022 18:20:16 -0800 [thread overview]
Message-ID: <20221108182016.59e27158@kernel.org> (raw)
In-Reply-To: <PAXPR04MB918598BE192BEF2B5E7CF678893E9@PAXPR04MB9185.eurprd04.prod.outlook.com>
On Wed, 9 Nov 2022 02:15:28 +0000 Shenwei Wang wrote:
> > This set doesn't apply to net-next, is it on top of some not-yet-applied patches ?
>
> I saw the first patch " net: fec: simplify the code logic of quirks" had already been
> applied a day ago. May only need to apply the second one: " net: fec: add xdp and page pool statistics".
Oh, I see. You can wait for reviews a bit longer, but you'll have
to repost just the parts that can be applied separately.
It's fairly tricky to skip the first patch when applying,
and the build bot will definitely not be able to cope.
prev parent reply other threads:[~2022-11-09 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 17:21 [PATCH v2 0/2] net: fec: optimization and statistics Shenwei Wang
2022-11-08 17:21 ` [PATCH v2 1/2] net: fec: simplify the code logic of quirks Shenwei Wang
2022-11-08 17:21 ` [PATCH v2 2/2] net: fec: add xdp and page pool statistics Shenwei Wang
2022-11-09 1:57 ` [PATCH v2 0/2] net: fec: optimization and statistics Jakub Kicinski
2022-11-09 2:15 ` [EXT] " Shenwei Wang
2022-11-09 2:20 ` Jakub Kicinski [this message]
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=20221108182016.59e27158@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=imx@lists.linux.dev \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenwei.wang@nxp.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).