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 5.5
Date: Mon, 30 Dec 2019 20:31:40 +0900	[thread overview]
Message-ID: <8483f2c2-626d-382f-3994-ee29daebff75@i-love.sakura.ne.jp> (raw)

Hello Linus,

This is my first time for sending pull requests. It seems that most people
create a tag signed with GPG key but a few people send pull requests on
master branch without signing with GPG key. Did I follow necessary steps?
---
The following changes since commit 6794862a16ef41f753abd75c03a152836e4c8028:

  Merge tag 'for-5.5-rc1-kconfig-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2019-12-09 12:14:31 -0800)

are available in the git repository at:

  git://git.osdn.net/gitroot/tomoyo/tomoyo-test1.git master

for you to fetch changes up to 6bd5ce6089b561f5392460bfb654dea89356ab1b:

  tomoyo: Suppress RCU warning at list_for_each_entry_rcu(). (2019-12-16 23:02:27 +0900)

----------------------------------------------------------------
Tetsuo Handa (2):
      tomoyo: Don't use nifty names on sockets.
      tomoyo: Suppress RCU warning at list_for_each_entry_rcu().

 security/tomoyo/common.c   |  9 ++++++---
 security/tomoyo/domain.c   | 15 ++++++++++-----
 security/tomoyo/group.c    |  9 ++++++---
 security/tomoyo/realpath.c | 32 +-------------------------------
 security/tomoyo/util.c     |  6 ++++--
 5 files changed, 27 insertions(+), 44 deletions(-)

             reply	other threads:[~2019-12-30 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 11:31 Tetsuo Handa [this message]
2019-12-30 20:14 ` [GIT PULL] tomoyo fixes for 5.5 Linus Torvalds
2019-12-31  1:36   ` Tetsuo Handa
2019-12-31 19:45 ` 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=8483f2c2-626d-382f-3994-ee29daebff75@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.