public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Cui GaoSheng <cuigaosheng1@huawei.com>,
	Hulk Robot <hulkci@huawei.com>, Kees Cook <keescook@chromium.org>,
	Kenta Tada <Kenta.Tada@sony.com>
Subject: [GIT PULL] seccomp updates for v5.13-rc1
Date: Mon, 26 Apr 2021 11:29:05 -0700	[thread overview]
Message-ID: <202104261127.43AC34A519@keescook> (raw)

Hi Linus,

Please pull these tiny seccomp updates for v5.13-rc1.

Thanks!

-Kees

The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:

  Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.13-rc1

for you to fetch changes up to a3fc712c5b37aec802438fe0de095d7f6f3827a3:

  seccomp: Fix "cacheable" typo in comments (2021-03-30 22:34:30 -0700)

----------------------------------------------------------------
seccomp updates for v5.13-rc1

- Fix "cacheable" typo in comments (Cui GaoSheng)

- Fix CONFIG for /proc/$pid/status Seccomp_filters (Kenta.Tada@sony.com)

----------------------------------------------------------------
Cui GaoSheng (1):
      seccomp: Fix "cacheable" typo in comments

Kenta.Tada@sony.com (1):
      seccomp: Fix CONFIG tests for Seccomp_filters

 fs/proc/array.c  | 2 ++
 init/init_task.c | 2 +-
 kernel/seccomp.c | 2 +-
 3 files changed, 4 insertions(+), 2 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2021-04-26 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 18:29 Kees Cook [this message]
2021-04-27 17:37 ` [GIT PULL] seccomp updates for v5.13-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=202104261127.43AC34A519@keescook \
    --to=keescook@chromium.org \
    --cc=Kenta.Tada@sony.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=hulkci@huawei.com \
    --cc=linux-kernel@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