linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>,
	Kees Cook <keescook@chromium.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Will Drewry <wad@chromium.org>
Subject: [GIT PULL] seccomp update for v6.3-rc1
Date: Fri, 17 Feb 2023 11:17:42 -0800	[thread overview]
Message-ID: <63efd2d6.170a0220.c7721.6d38@mx.google.com> (raw)

Hi Linus,

Please pull this tiny seccomp update for v6.3-rc1. In the future, I may
collapse these kinds of tiny changes into my larger kernel hardening tree,
but figured I wouldn't do it this time without a heads-up. :)

Thanks!

-Kees

The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:

  Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.3-rc1

for you to fetch changes up to 0fb0624b15d21622c214617fda5c05a203b04564:

  seccomp: fix kernel-doc function name warning (2023-01-13 17:01:06 -0800)

----------------------------------------------------------------
seccomp update for v6.3-rc1

- Fix kernel-doc function name ordering to avoid warning (Randy Dunlap)

----------------------------------------------------------------
Randy Dunlap (1):
      seccomp: fix kernel-doc function name warning

 kernel/seccomp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
Kees Cook

             reply	other threads:[~2023-02-17 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 19:17 Kees Cook [this message]
2023-02-21 19:29 ` [GIT PULL] seccomp update for v6.3-rc1 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=63efd2d6.170a0220.c7721.6d38@mx.google.com \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wad@chromium.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;
as well as URLs for NNTP newsgroup(s).