mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LSM List <linux-security-module@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Casey Schaufler <casey@schaufler-ca.com>,
	Konstantin Andreev <andreev@swemel.ru>
Subject: [GIT PULL] Smack patches for 6.14
Date: Tue, 21 Jan 2025 14:23:11 -0800	[thread overview]
Message-ID: <e79d21e2-1491-491f-b46d-9bd814290771@schaufler-ca.com> (raw)
In-Reply-To: <e79d21e2-1491-491f-b46d-9bd814290771.ref@schaufler-ca.com>

Hello Linus,

Here is the Smack pull request for v6.14.

There is one patch. It removes a small code duplication.

The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

  https://github.com/cschaufler/smack-next tags/Smack-for-6.14

for you to fetch changes up to 6f71ad02aae83f7032255863e374acadaa852bea:

  smack: deduplicate access to string conversion (2024-12-06 13:21:12 -0800)

----------------------------------------------------------------
One minor code improvement for v6.14

----------------------------------------------------------------
Konstantin Andreev (1):
      smack: deduplicate access to string conversion

 security/smack/smack.h        |  1 +
 security/smack/smack_access.c | 10 ++++++++--
 security/smack/smack_lsm.c    | 18 +-----------------
 security/smack/smackfs.c      | 26 +++++---------------------
 4 files changed, 15 insertions(+), 40 deletions(-)


       reply	other threads:[~2025-01-21 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e79d21e2-1491-491f-b46d-9bd814290771.ref@schaufler-ca.com>
2025-01-21 22:23 ` Casey Schaufler [this message]
2025-01-22  4: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=e79d21e2-1491-491f-b46d-9bd814290771@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=andreev@swemel.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.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

all inboxes | Powered by JetHome®