From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Ken Goldman <kgold@linux.ibm.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, 13 Sep 2023 16:16:24 +0200 [thread overview]
Message-ID: <ea3dc0b080d6ed56c2f90793017d2908ba15718f.camel@huaweicloud.com> (raw)
In-Reply-To: <5800e76f-bae5-b3c8-9d0d-51584c93d4ad@linux.ibm.com>
On Wed, 2023-09-06 at 16:54 -0400, Ken Goldman wrote:
> Jonathan: What should be my next step?
>
> On 9/4/2023 5:52 PM, Jarkko Sakkinen wrote:
> > On Fri Sep 1, 2023 at 12:46 AM EEST, Ken Goldman wrote:
> > > Thank you.
> > >
> > > Do you know the process for getting this accepted into the kernel
> > > documentation.
> >
> > The bulk of the work would be to convert it ReStructured Text and
> > follow the guidelines in https://docs.kernel.org/doc-guide/index.html
>
> I think I did that. The source .rst is at
> https://github.com/IBM/ima-doc
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/
Thanks
Roberto
> >
> > You should also CC the documentation patches to:
> >
> > * Jonathan Corbet <corbet@lwn.net> (maintainer of the documentation)
> > * linux-doc@vger.kernel.org
>
> Thank you for this.
>
> >
> > Perhaps Mimi could help out formalizing this together so I suggest to
> > work with her. I'm also happy to review the documentation once the
> > patches are out.
>
> Mimi worked with me from the beginning.
next prev parent reply other threads:[~2023-09-13 14:16 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 [this message]
2023-09-20 19:02 ` Ken Goldman
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=ea3dc0b080d6ed56c2f90793017d2908ba15718f.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=corbet@lwn.net \
--cc=jarkko@kernel.org \
--cc=kgold@linux.ibm.com \
--cc=linux-integrity@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox