From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH 2/2] tomoyo: Fixed typo in documentation
Date: Mon, 9 Nov 2020 13:45:05 +0900 [thread overview]
Message-ID: <7d214f98-90bb-563e-fbc1-e812e31f3b71@i-love.sakura.ne.jp> (raw)
In-Reply-To: <7c60a6f5-414f-99e8-68c3-ca3b60fe89e9@nvidia.com>
On 2020/11/09 13:17, John Hubbard wrote:
> On 11/8/20 7:41 PM, Souptick Joarder wrote:
>> John, as patch[1/2] is dropped, can we take this patch forward with some more
>> updates in documentations ?
>>
>
> That's really up to the folks who work on this code. Personally I would rarely
> post a patch *just* for this, but on the other hand it is a correction. Either
> way is fine with me of course.
Xiaoming Ni has posted a patch for fixing spelling errors in security/ directory
at https://lkml.kernel.org/r/20200822030534.2577-1-nixiaoming@huawei.com .
James, can we apply that patch? Or, should we split that patch into each subsystem?
next prev parent reply other threads:[~2020-11-09 4:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 8:24 [PATCH 1/2] tomoyo: Convert get_user_pages*() to pin_user_pages*() Souptick Joarder
2020-11-07 8:24 ` [PATCH 2/2] tomoyo: Fixed typo in documentation Souptick Joarder
2020-11-07 8:57 ` John Hubbard
2020-11-09 3:41 ` Souptick Joarder
2020-11-09 4:17 ` John Hubbard
2020-11-09 4:45 ` Tetsuo Handa [this message]
2020-11-10 3:08 ` James Morris
2020-11-07 9:04 ` [PATCH 1/2] tomoyo: Convert get_user_pages*() to pin_user_pages*() John Hubbard
2020-11-07 19:17 ` John Hubbard
2020-11-08 1:13 ` Tetsuo Handa
2020-11-08 2:17 ` John Hubbard
2020-11-08 4:12 ` Tetsuo Handa
2020-11-08 5:00 ` John Hubbard
2020-11-09 3:38 ` Souptick Joarder
2020-11-09 3:36 ` Souptick Joarder
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=7d214f98-90bb-563e-fbc1-e812e31f3b71@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.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.