public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Networking <netdev@vger.kernel.org>,
	linux-hams@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Andreas Koensgen <ajk@comnets.uni-bremen.de>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH net-next 0/2] networking docs section headings cleanup
Date: Fri, 17 Oct 2025 13:45:24 +0700	[thread overview]
Message-ID: <20251017064525.28836-2-bagasdotme@gmail.com> (raw)

Hi,

Just two net docs patches cleaning up section headings. The shortlog below
should be self-explanatory.

Enjoy!

Bagas Sanjaya (2):
  net: nfc: Format userspace interface subsection headings
  net: 6pack: Demote "How to turn on 6pack support" section heading

 Documentation/networking/6pack.rst | 2 +-
 Documentation/networking/nfc.rst   | 6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)


base-commit: 7e0d4c111369ed385ec4aaa6c9c78c46efda54d0
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2025-10-17  6:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  6:45 Bagas Sanjaya [this message]
2025-10-17  6:45 ` [PATCH net-next 1/2] net: nfc: Format userspace interface subsection headings Bagas Sanjaya
2025-10-17  6:45 ` [PATCH net-next 2/2] net: 6pack: Demote "How to turn on 6pack support" section heading Bagas Sanjaya
2025-10-21  9:00 ` [PATCH net-next 0/2] networking docs section headings cleanup 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=20251017064525.28836-2-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=ajk@comnets.uni-bremen.de \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@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