From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: davem@davemloft.net, brouer@redhat.com, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, hawk@kernel.org,
ilias.apalodimas@linaro.org, linyunsheng@huawei.com,
alexander.duyck@gmail.com, Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH net-next v2 2/3] page_pool: allow caching from safely localized NAPI
Date: Fri, 14 Apr 2023 07:50:32 -0700 [thread overview]
Message-ID: <20230414075032.3b506d8c@kernel.org> (raw)
In-Reply-To: <dad5f7fc-dfa8-3aa9-ec4f-9e220e6f400f@redhat.com>
On Fri, 14 Apr 2023 10:45:44 +0200 Jesper Dangaard Brouer wrote:
> Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
Thanks!
> BTW, does it matter if I ack with <hawk@kernel.org> or <brouer@redhat.com> ?
>
> e.g. does the patchwork automation scripts, need to maintainer email to
> match?
For better or worse we don't have any substantial automation in
the area of maintainer ack tracking. But if we did we'd run it thru
various mail maps for sure, so it should be fine even then. I hope.
next prev parent reply other threads:[~2023-04-14 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 4:26 [PATCH net-next v2 0/3] page_pool: allow caching from safely localized NAPI Jakub Kicinski
2023-04-13 4:26 ` [PATCH net-next v2 1/3] net: skb: plumb napi state thru skb freeing paths Jakub Kicinski
2023-04-13 7:49 ` Yunsheng Lin
2023-04-13 8:51 ` Eric Dumazet
2023-04-14 0:57 ` Yunsheng Lin
2023-04-14 5:20 ` Jakub Kicinski
2023-04-14 9:40 ` Yunsheng Lin
2023-04-13 4:26 ` [PATCH net-next v2 2/3] page_pool: allow caching from safely localized NAPI Jakub Kicinski
2023-04-14 8:45 ` Jesper Dangaard Brouer
2023-04-14 14:50 ` Jakub Kicinski [this message]
2023-04-13 4:26 ` [PATCH net-next v2 3/3] bnxt: hook NAPIs to page pools Jakub Kicinski
2023-04-14 13:09 ` [PATCH net-next v2 0/3] page_pool: allow caching from safely localized NAPI Dragos Tatulea
2023-04-15 2:20 ` patchwork-bot+netdevbpf
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=20230414075032.3b506d8c@kernel.org \
--to=kuba@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.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).