From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, pabeni@redhat.com,
corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org,
andrew@lunn.ch, f.fainelli@gmail.com
Subject: Re: [PATCH net v3 00/14] docs: update and move the netdev-FAQ
Date: Thu, 31 Mar 2022 09:30:14 +0000 [thread overview]
Message-ID: <164871901464.21222.10495458574563491451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 29 Mar 2022 21:24:51 -0700 you wrote:
> A section of documentation for tree-specific process quirks had
> been created a while back. There's only one tree in it, so far,
> the tip tree, but the contents seem to answer similar questions
> as we answer in the netdev-FAQ. Move the netdev-FAQ.
>
> Take this opportunity to touch up and update a few sections.
>
> [...]
Here is the summary with links:
- [net,v3,01/14] docs: netdev: replace references to old archives
https://git.kernel.org/netdev/net/c/50386f7526dd
- [net,v3,02/14] docs: netdev: minor reword
https://git.kernel.org/netdev/net/c/30cddd30532a
- [net,v3,03/14] docs: netdev: move the patch marking section up
https://git.kernel.org/netdev/net/c/c82d90b14f6c
- [net,v3,04/14] docs: netdev: turn the net-next closed into a Warning
https://git.kernel.org/netdev/net/c/2fd4c50dbff1
- [net,v3,05/14] docs: netdev: note that RFC postings are allowed any time
https://git.kernel.org/netdev/net/c/0e242e3fb7a7
- [net,v3,06/14] docs: netdev: shorten the name and mention msgid for patch status
https://git.kernel.org/netdev/net/c/5d84921ac750
- [net,v3,07/14] docs: netdev: rephrase the 'Under review' question
https://git.kernel.org/netdev/net/c/8f785c1bb84f
- [net,v3,08/14] docs: netdev: rephrase the 'should I update patchwork' question
https://git.kernel.org/netdev/net/c/724c1a7443c5
- [net,v3,09/14] docs: netdev: add a question about re-posting frequency
https://git.kernel.org/netdev/net/c/b8ba106378a0
- [net,v3,10/14] docs: netdev: make the testing requirement more stringent
https://git.kernel.org/netdev/net/c/3eca381457ca
- [net,v3,11/14] docs: netdev: add missing back ticks
https://git.kernel.org/netdev/net/c/a30059731877
- [net,v3,12/14] docs: netdev: call out the merge window in tag checking
https://git.kernel.org/netdev/net/c/99eba4e5cbd4
- [net,v3,13/14] docs: netdev: broaden the new vs old code formatting guidelines
https://git.kernel.org/netdev/net/c/08767a26f095
- [net,v3,14/14] docs: netdev: move the netdev-FAQ to the process pages
https://git.kernel.org/netdev/net/c/8df0136376dc
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-03-31 9:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 4:24 [PATCH net v3 00/14] docs: update and move the netdev-FAQ Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 01/14] docs: netdev: replace references to old archives Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 02/14] docs: netdev: minor reword Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 03/14] docs: netdev: move the patch marking section up Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 04/14] docs: netdev: turn the net-next closed into a Warning Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 05/14] docs: netdev: note that RFC postings are allowed any time Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 06/14] docs: netdev: shorten the name and mention msgid for patch status Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 07/14] docs: netdev: rephrase the 'Under review' question Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 08/14] docs: netdev: rephrase the 'should I update patchwork' question Jakub Kicinski
2022-03-30 23:40 ` Florian Fainelli
2022-03-30 4:25 ` [PATCH net v3 09/14] docs: netdev: add a question about re-posting frequency Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 10/14] docs: netdev: make the testing requirement more stringent Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 11/14] docs: netdev: add missing back ticks Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 12/14] docs: netdev: call out the merge window in tag checking Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 13/14] docs: netdev: broaden the new vs old code formatting guidelines Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 14/14] docs: netdev: move the netdev-FAQ to the process pages Jakub Kicinski
2022-03-31 9: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=164871901464.21222.10495458574563491451.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.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;
as well as URLs for NNTP newsgroup(s).