From: Jakub Kicinski <kuba@kernel.org>
To: Shailend Chand <shailend@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
almasrymina@google.com, edumazet@google.com,
hramamurthy@google.com, jeroendb@google.com, pabeni@redhat.com,
pkaligineedi@google.com, rushilg@google.com, willemb@google.com,
ziweixiao@google.com
Subject: Re: [PATCH net-next v2 00/10] gve: Implement queue api
Date: Mon, 6 May 2024 18:25:20 -0700 [thread overview]
Message-ID: <20240506182520.67044aa7@kernel.org> (raw)
In-Reply-To: <CANLc=avO2Xmkjh=VsvCkN=jUEOpSFN-74MkbtByicsRs+GANNQ@mail.gmail.com>
On Mon, 6 May 2024 11:07:52 -0700 Shailend Chand wrote:
> > The last patch of this patchset did not get applied:
> > https://patchwork.kernel.org/project/netdevbpf/patch/20240430231420.699177-11-shailend@google.com/,
> > not sure why there is a "no matching commit" message.
>
> This is the v2 patch that did not get applied
> https://patchwork.kernel.org/project/netdevbpf/patch/20240501232549.1327174-11-shailend@google.com/.
> The subjects of the cover letter and this patch both are the same,
> differing only in their number prefix, maybe that could be triggering
> some issue.
The space characters in Mina's review tag are funny looking, maybe that
was the cause. In any case, applied now, will push once build finishes.
Thanks!
prev parent reply other threads:[~2024-05-07 1:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 23:25 [PATCH net-next v2 00/10] gve: Implement queue api Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 01/10] queue_api: define " Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 02/10] gve: Make the GQ RX free queue funcs idempotent Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 03/10] gve: Add adminq funcs to add/remove a single Rx queue Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 04/10] gve: Make gve_turn(up|down) ignore stopped queues Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 05/10] gve: Make gve_turnup work for nonempty queues Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 06/10] gve: Avoid rescheduling napi if on wrong cpu Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 07/10] gve: Reset Rx ring state in the ring-stop funcs Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 08/10] gve: Account for stopped queues when reading NIC stats Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 09/10] gve: Alloc and free QPLs with the rings Shailend Chand
2024-05-01 23:25 ` [PATCH net-next v2 10/10] gve: Implement queue api Shailend Chand
2024-05-06 18:09 ` David Wei
2024-05-06 18:47 ` Mina Almasry
2024-05-07 21:06 ` David Wei
2024-05-08 17:09 ` Mina Almasry
2024-05-09 17:46 ` David Wei
2024-05-02 15:15 ` [PATCH net-next v2 00/10] " Willem de Bruijn
2024-05-05 13:40 ` patchwork-bot+netdevbpf
2024-05-06 17:41 ` Shailend Chand
2024-05-06 18:07 ` Shailend Chand
2024-05-07 1:25 ` 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=20240506182520.67044aa7@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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).