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, corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, andrew@lunn.ch,
jesse.brandeburg@intel.com, sd@queasysnail.net,
horms@verge.net.au, przemyslaw.kitszel@intel.com,
f.fainelli@gmail.com, jiri@resnulli.us, ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next v2] docs: try to encourage (netdev?) reviewers
Date: Sun, 15 Oct 2023 13:30:24 +0000 [thread overview]
Message-ID: <169737662407.24568.3374449097895161500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231011024224.161282-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 10 Oct 2023 19:42:24 -0700 you wrote:
> Add a section to netdev maintainer doc encouraging reviewers
> to chime in on the mailing list.
>
> The questions about "when is it okay to share feedback"
> keep coming up (most recently at netconf) and the answer
> is "pretty much always".
>
> [...]
Here is the summary with links:
- [net-next,v2] docs: try to encourage (netdev?) reviewers
https://git.kernel.org/netdev/net-next/c/6e55b1cbf05d
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:[~2023-10-15 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 2:42 [PATCH net-next v2] docs: try to encourage (netdev?) reviewers Jakub Kicinski
2023-10-11 8:47 ` Bagas Sanjaya
2023-10-12 0:14 ` Florian Fainelli
2023-10-12 7:55 ` Martin Habets
2023-10-15 13:30 ` 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=169737662407.24568.3374449097895161500.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@verge.net.au \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sd@queasysnail.net \
--cc=workflows@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.