From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
dsahern@gmail.com, "helpdesk@kernel.org" <helpdesk@kernel.org>
Subject: Re: [PATCH net-next v2 0/2] net: create device lookup API with reference tracking
Date: Thu, 15 Jun 2023 16:22:28 -0400 [thread overview]
Message-ID: <20230615-praying-viper-e71c8b@meerkat> (raw)
In-Reply-To: <20230615131747.49e9238e@kernel.org>
On Thu, Jun 15, 2023 at 01:17:47PM -0700, Jakub Kicinski wrote:
> Oh, that could well be it, I did! Linus asked people to do that
> recently, I think in the -rc4 email. One of the RC emails, anyway.
> IDK how many people listened to Linus. Technically it only matters
> for maintainers who may send PRs to him, otherwise he said his diffstat
> will be different than the one in the PR.
>
> But it's not just me:
> https://lore.kernel.org/all/168674222282.23990.8151831714077509932.git-patchwork-notify@kernel.org/
> https://lore.kernel.org/all/168661442392.10094.4616497599019441750.git-patchwork-notify@kernel.org/
> (there's a third one but it's is also Matthieu so CBA to get the lore
> link, we're just counting people.)
>
> Could the bot try matching in histogram and non-histogram mode?
Yes, I'll see if I can teach the bot to regenerate the diff with --histogram
when there is no match.
-K
next prev parent reply other threads:[~2023-06-15 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 21:49 [PATCH net-next v2 0/2] net: create device lookup API with reference tracking Jakub Kicinski
2023-06-12 21:49 ` [PATCH net-next v2 1/2] " Jakub Kicinski
2023-06-13 9:14 ` Eric Dumazet
2023-06-14 2:19 ` David Ahern
2023-06-16 8:21 ` Eric Dumazet
2023-06-17 0:10 ` David Ahern
2023-06-12 21:49 ` [PATCH net-next v2 2/2] netpoll: allocate netdev tracker right away Jakub Kicinski
2023-06-15 7:50 ` [PATCH net-next v2 0/2] net: create device lookup API with reference tracking patchwork-bot+netdevbpf
2023-06-15 17:00 ` Jakub Kicinski
2023-06-15 19:41 ` Konstantin Ryabitsev
2023-06-15 20:17 ` Jakub Kicinski
2023-06-15 20:22 ` Konstantin Ryabitsev [this message]
2023-06-15 21:56 ` 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=20230615-praying-viper-e71c8b@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=helpdesk@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@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).