From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Paul Moore <paul@paul-moore.com>
Cc: corbet@lwn.net, casey@schaufler-ca.com, omosnace@redhat.com,
john.johansen@canonical.com, kpsingh@kernel.org,
bpf@vger.kernel.org, linux-doc@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH 1/2] lsm: Fix description of fs_context_parse_param
Date: Mon, 12 Dec 2022 09:33:58 +0100 [thread overview]
Message-ID: <8b202f4e2e234e6786b1c078129e2c3e6853c404.camel@huaweicloud.com> (raw)
In-Reply-To: <CAHC9VhSKeTqR+m5g2Nacp9ZJbvD3=OADGMEfDRX4rsH8HmGO9g@mail.gmail.com>
On Fri, 2022-12-09 at 12:28 -0500, Paul Moore wrote:
> On Fri, Dec 9, 2022 at 3:30 AM Roberto Sassu
> <roberto.sassu@huaweicloud.com> wrote:
> > From: Roberto Sassu <roberto.sassu@huawei.com>
> >
> > The fs_context_parse_param hook already has a description, which seems the
> > right one according to the code.
> >
> > Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> > ---
> > include/linux/lsm_hooks.h | 3 ---
> > 1 file changed, 3 deletions(-)
>
> I just merged this into lsm/next with a 'Fixes' tag pointing at the
> previous comment block commit, thanks Roberto.
Thanks Paul. Didn't include it, as I thought it is part of the stable
kernel process. I guess it is always fine to include it, and to not CC
the stable kernel mailing list, when the patch does not meet the
criteria.
Roberto
next prev parent reply other threads:[~2022-12-12 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 8:29 [PATCH 1/2] lsm: Fix description of fs_context_parse_param Roberto Sassu
2022-12-09 8:29 ` [PATCH 2/2] doc: Fix fs_context_parse_param description in mount_api.rst Roberto Sassu
2022-12-09 17:41 ` Paul Moore
2022-12-12 8:35 ` Roberto Sassu
2022-12-09 17:28 ` [PATCH 1/2] lsm: Fix description of fs_context_parse_param Paul Moore
2022-12-12 8:33 ` Roberto Sassu [this message]
2022-12-12 20:19 ` Paul Moore
2022-12-14 1:08 ` patchwork-bot+netdevbpf
2022-12-14 2:43 ` Paul Moore
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=8b202f4e2e234e6786b1c078129e2c3e6853c404.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=john.johansen@canonical.com \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
/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).