From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net] docs: netdev: correct the heading level for co-posting selftests
Date: Fri, 27 Jun 2025 07:48:58 +0700 [thread overview]
Message-ID: <aF3qeuJupkykvtpV@archie.me> (raw)
In-Reply-To: <20250626182055.4161905-1-kuba@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On Thu, Jun 26, 2025 at 11:20:55AM -0700, Jakub Kicinski wrote:
> "Co-posting selftests" belongs in the "netdev patch review" section,
> same as "co-posting changes to user space components". It was
> erroneously added as its own section.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: corbet@lwn.net
> CC: linux-doc@vger.kernel.org
> ---
> Documentation/process/maintainer-netdev.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst
> index 1ac62dc3a66f..e1755610b4bc 100644
> --- a/Documentation/process/maintainer-netdev.rst
> +++ b/Documentation/process/maintainer-netdev.rst
> @@ -312,7 +312,7 @@ Posting as one thread is discouraged because it confuses patchwork
> (as of patchwork 2.2.2).
>
> Co-posting selftests
> ---------------------
> +~~~~~~~~~~~~~~~~~~~~
>
> Selftests should be part of the same series as the code changes.
> Specifically for fixes both code change and related test should go into
Looks good, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-27 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 18:20 [PATCH net] docs: netdev: correct the heading level for co-posting selftests Jakub Kicinski
2025-06-27 0:48 ` Bagas Sanjaya [this message]
2025-06-27 22:40 ` patchwork-bot+netdevbpf
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=aF3qeuJupkykvtpV@archie.me \
--to=bagasdotme@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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).