From: "Serge E. Hallyn" <serge@hallyn.com>
To: torvalds@linux-foundation.org
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Paul Moore <paul@paul-moore.com>
Subject: [GIT PULL] capabilities update for 6.15
Date: Thu, 27 Mar 2025 23:07:26 -0500 [thread overview]
Message-ID: <20250328040726.GA423659@mail.hallyn.com> (raw)
Hi Linus,
this PR just contains one patch to drop an unused helper. Please merge.
thanks,
-serge
--
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git tags/caps-pr-20250327
for you to fetch changes up to 4ae89b1fe7c2e37a8f2ea39765e4c40c9d42a101:
capability: Remove unused has_capability (2025-03-07 22:03:09 -0600)
----------------------------------------------------------------
Capabilities update for 6.15
This branch contains one patch:
capability: Remove unused has_capability
This removes a helper function whose last user (smack) stopped using
it in 2018.
This has been in linux-next for most of the the last cycle with no
apparent issues. It is available at:
git@git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git #caps-20250327
on top of commit 2014c95afecee3e76ca4a56956a936e23283f05b (tag: v6.14-rc1)
----------------------------------------------------------------
Dr. David Alan Gilbert (1):
capability: Remove unused has_capability
include/linux/capability.h | 5 -----
kernel/capability.c | 16 ----------------
security/commoncap.c | 9 +++++----
3 files changed, 5 insertions(+), 25 deletions(-)
next reply other threads:[~2025-03-28 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 4:07 Serge E. Hallyn [this message]
2025-03-28 20:41 ` [GIT PULL] capabilities update for 6.15 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=20250328040726.GA423659@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@treblig.org \
--cc=paul@paul-moore.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.