From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, bpf@vger.kernel.org,
jesse.brandeburg@intel.com, linux-doc@vger.kernel.org,
corbet@lwn.net
Subject: Re: [PATCH net] docs: netdev: offer performance feedback to contributors
Date: Mon, 24 Oct 2022 10:10:15 +0000 [thread overview]
Message-ID: <166660621587.6109.10588903646372875602.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221020183031.1245964-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 20 Oct 2022 11:30:31 -0700 you wrote:
> Some of us gotten used to producing large quantities of peer feedback
> at work, every 3 or 6 months. Extending the same courtesy to community
> members seems like a logical step. It may be hard for some folks to
> get validation of how important their work is internally, especially
> at smaller companies which don't employ many kernel experts.
>
> The concept of "peer feedback" may be a hyperscaler / silicon valley
> thing so YMMV. Hopefully we can build more context as we go.
>
> [...]
Here is the summary with links:
- [net] docs: netdev: offer performance feedback to contributors
https://git.kernel.org/netdev/net/c/c5884ef477b4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-24 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 18:30 [PATCH net] docs: netdev: offer performance feedback to contributors Jakub Kicinski
2022-10-24 10:10 ` patchwork-bot+netdevbpf [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=166660621587.6109.10588903646372875602.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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