[GIT PULL] SafeSetID changes for v5.13

From: Micah Morton <mortonm@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-security-module <linux-security-module@vger.kernel.org>
Subject: [GIT PULL] SafeSetID changes for v5.13
Date: Mon, 3 May 2021 11:42:13 -1000	[thread overview]
Message-ID: <CAJ-EccOdLW1+8xx8=PRHzSjy4kVaVOUave0pAXF5b=cD4w3=pg@mail.gmail.com> (raw)

The following changes since commit 9f4ad9e425a1d3b6a34617b8ea226d56a119a717:

  Linux 5.12 (2021-04-25 13:49:08 -0700)

are available in the Git repository at:

  https://github.com/micah-morton/linux.git tags/safesetid-5.13

for you to fetch changes up to 1ca86ac1ec8d201478e9616565d4df5d51595cfc:

  LSM: SafeSetID: Fix code specification by scripts/checkpatch.pl
(2021-04-26 16:36:50 -0700)

----------------------------------------------------------------
Simple code cleanup

This pull request just has a single 3-line code cleanup commit to eliminate
some unreachable 'break' statements that come after 'return's. No
other work was done on SafeSetID for the 5.13 merge window.

The commit has been in linux-next since 4-26-2021. I forgot to add the commit
to linux-next until after the 5.13 merge window started, which is why the commit
is on top of the 5.12 release. I'm not really sure which
release/commit the patch author based the commit on, but doesn't seem
to matter in this case since the commit is obviously correct from
looking at the code and the commit applied cleanly on top of 5.12 --
so I don't see applying this on top of 5.12 as a case of losing any of
the testing/development history of the commit.

----------------------------------------------------------------
Yanwei Gao (1):
      LSM: SafeSetID: Fix code specification by scripts/checkpatch.pl

 security/safesetid/lsm.c | 3 ---
 1 file changed, 3 deletions(-)