All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkML <linux-kernel@vger.kernel.org>,
	Casey Schaufler <casey@schaufler-ca.com>,
	Linux Security Module list 
	<linux-security-module@vger.kernel.org>
Subject: [GIT PULL] Smack patches for v5.11
Date: Tue, 15 Dec 2020 11:02:53 -0800	[thread overview]
Message-ID: <7bb1c722-0a4f-2799-6421-5c3741e7c106@schaufler-ca.com> (raw)
In-Reply-To: 7bb1c722-0a4f-2799-6421-5c3741e7c106.ref@schaufler-ca.com

Hello Linus

Here are the Smack tree changes for the v5.11 release. There are no functional
changes. There a code clean-up and some function header comment corrections.


--
The following changes since commit f8394f232b1eab649ce2df5c5f15b0e528c92091:

  Linux 5.10-rc3 (2020-11-08 16:10:16 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 9b0072e2b2b588ad75c94f2c6e6c52c8f4bd2657:

  security/smack: remove unused varible 'rc' (2020-11-16 17:26:31 -0800)

----------------------------------------------------------------
Smack updates for Linux 5.11. One minor code clean-up and a
set of corrections in function header comments.

----------------------------------------------------------------
Alex Shi (2):
      Smack: fix kernel-doc interface on functions
      security/smack: remove unused varible 'rc'

 security/smack/smack_lsm.c | 3 +--
 security/smack/smackfs.c   | 7 ++++---
 2 files changed, 5 insertions(+), 5 deletions(-)



       reply	other threads:[~2020-12-15 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7bb1c722-0a4f-2799-6421-5c3741e7c106.ref@schaufler-ca.com>
2020-12-15 19:02 ` Casey Schaufler [this message]
2020-12-16 19:44   ` [GIT PULL] Smack patches for v5.11 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=7bb1c722-0a4f-2799-6421-5c3741e7c106@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --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 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.