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, f.fainelli@gmail.com, andrew@lunn.ch,
rdunlap@infradead.org
Subject: Re: [PATCH net v2 0/2] netdev doc de-FAQization
Date: Wed, 28 Dec 2022 10:10:15 +0000 [thread overview]
Message-ID: <167222221589.7103.10053124658116345424.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221222192248.1265007-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 22 Dec 2022 11:22:46 -0800 you wrote:
> We have outgrown the FAQ format for our process doc.
> I often find myself struggling to locate information in this doc,
> because the questions do not serve well as section headers.
> Reformat the document.
>
> v2: update the headers
> v1: https://lore.kernel.org/all/20221221184007.1170384-1-kuba@kernel.org/
>
> [...]
Here is the summary with links:
- [net,v2,1/2] docs: netdev: reshuffle sections in prep for de-FAQization
https://git.kernel.org/netdev/net/c/f4ef681115f8
- [net,v2,2/2] docs: netdev: convert to a non-FAQ document
https://git.kernel.org/netdev/net/c/ff249be5cca9
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-12-28 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 19:22 [PATCH net v2 0/2] netdev doc de-FAQization Jakub Kicinski
2022-12-22 19:22 ` [PATCH net v2 1/2] docs: netdev: reshuffle sections in prep for de-FAQization Jakub Kicinski
2022-12-22 19:22 ` [PATCH net v2 2/2] docs: netdev: convert to a non-FAQ document Jakub Kicinski
2022-12-28 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=167222221589.7103.10053124658116345424.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.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).