From: "Serge E. Hallyn" <serge@hallyn.com>
To: torvalds@linux-foundation.org,
linux-security-module@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [GIT PULL] capabilities update for v7.3
Date: Sat, 22 Aug 2026 09:50:03 -0500 [thread overview]
Message-ID: <aom3Gwl3GkBpw4fr@mail.hallyn.com> (raw)
Hi Linus,
Just one trivial patch fixing up documentation.
thanks,
-serge
The following changes since commit 1590cf0329716306e948a8fc29f1d3ee87d3989f:
Linux 7.2-rc4 (2026-07-19 13:54:41 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git tags/caps-pr-20260820
for you to fetch changes up to 9b0ee13b80798feb0e6a83a6d69e915f23fcb6bc:
capability: remove non-kernel-doc comments (2026-07-24 07:35:47 -0500)
----------------------------------------------------------------
Capabilities update for 7.3
This branch contains just one trivial patch:
capability: remove non-kernel-doc comments
which corrects two comments to avoid kernel-doc warnings. It's available at
git@git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git #caps-20260820
on top of commit 1590cf0329716306e948a8fc29f1d3ee87d3989f (tag: v7.2-rc4)
----------------------------------------------------------------
Randy Dunlap (1):
capability: remove non-kernel-doc comments
include/uapi/linux/capability.h | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2026-08-22 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 14:50 Serge E. Hallyn [this message]
2026-08-22 16:15 ` [GIT PULL] capabilities update for v7.3 Linus Torvalds
2026-08-22 21:06 ` Serge E. Hallyn
2026-08-22 16:18 ` pr-tracker-bot
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=aom3Gwl3GkBpw4fr@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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