From: Ken Goldman <kgold@linux.ibm.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Linux Integrity <linux-integrity@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Subject: Re: Linux IMA documentation
Date: Wed, 20 Sep 2023 15:02:47 -0400 [thread overview]
Message-ID: <087c8835-5f4b-4df3-8a7e-30b95c78a8c0@linux.ibm.com> (raw)
In-Reply-To: <ea3dc0b080d6ed56c2f90793017d2908ba15718f.camel@huaweicloud.com>
On 9/13/2023 10:16 AM, Roberto Sassu wrote:
> I think your document is a good candidate for being put in
> Documentation/admin-guide/LSM/, once my patch set is upstreamed:
> https://lore.kernel.org/linux-integrity/20230904133415.1799503-1-roberto.sassu@huaweicloud.com/
Isn't the documentation separate from this proposed patch? It doesn't
claim to document how code works.
What's the process for proposing this work for inclusion in the
documentation?
next prev parent reply other threads:[~2023-09-20 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:42 Linux IMA documentation Ken Goldman
2023-08-17 16:04 ` Jarkko Sakkinen
2023-08-31 21:46 ` Ken Goldman
2023-09-04 21:52 ` Jarkko Sakkinen
2023-09-06 20:54 ` Ken Goldman
2023-09-13 14:16 ` Roberto Sassu
2023-09-20 19:02 ` Ken Goldman [this message]
2023-09-20 19:55 ` Mimi Zohar
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=087c8835-5f4b-4df3-8a7e-30b95c78a8c0@linux.ibm.com \
--to=kgold@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=roberto.sassu@huaweicloud.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