All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module <linux-security-module@vger.kernel.org>
Subject: [GIT PULL] tomoyo fixes for v5.11
Date: Mon, 14 Dec 2020 13:21:46 +0900	[thread overview]
Message-ID: <85aa37f5-3fca-fde2-068d-b1888de51457@i-love.sakura.ne.jp> (raw)

The following changes since commit 15269fb193108ba8a3774507d0bbd70949ab610d:

  tomoyo: Fix typo in comments. (2020-12-06 13:44:57 +0900)

are available in the git repository at:

  git://git.osdn.net/gitroot/tomoyo/tomoyo-test1.git tags/tomoyo-pr-20201214

for you to fetch changes up to 15269fb193108ba8a3774507d0bbd70949ab610d:

  tomoyo: Fix typo in comments. (2020-12-06 13:44:57 +0900)

----------------------------------------------------------------
Limit recursion depth, fix clang warning, fix comment typo, and
silence memory allocation failure warning.

tomoyo: fix clang pointer arithmetic warning
tomoyo: Limit wildcard recursion depth.
tomoyo: Fix null pointer check
tomoyo: Fix typo in comments.

 security/tomoyo/audit.c         |    2 -
 security/tomoyo/common.c        |    8 ++---
 security/tomoyo/condition.c     |    2 -
 security/tomoyo/domain.c        |    6 +---
 security/tomoyo/gc.c            |    2 -
 security/tomoyo/memory.c        |    4 +-
 security/tomoyo/securityfs_if.c |    6 ++--
 security/tomoyo/util.c          |   55 +++++++++++++++++++++-------------------
 8 files changed, 44 insertions(+), 41 deletions(-)

----------------------------------------------------------------

             reply	other threads:[~2020-12-14  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  4:21 Tetsuo Handa [this message]
2020-12-14 20:56 ` [GIT PULL] tomoyo fixes 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=85aa37f5-3fca-fde2-068d-b1888de51457@i-love.sakura.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --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.