Linux Documentation
 help / color / mirror / Atom feed
From: John Doe <drapl0n.kernel@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Paul Moore <paul@paul-moore.com>,
	Serge Hallyn <sergeh@kernel.org>,
	 Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	 linux-security-module@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix typo and formattting in security/credentials.rst
Date: Thu, 7 May 2026 13:48:55 -0400	[thread overview]
Message-ID: <afzQVIv4-Up24VNM@gmail.com> (raw)
In-Reply-To: <cbe6e145-9d2f-47bb-8d22-1599cfd1a9d4@infradead.org>

On Wed, May 06, 2026 at 05:36:53PM -0700, Randy Dunlap wrote:
> Hi,
> 
> On 5/6/26 3:59 PM, Mayank Gite wrote:
> > - Fixes a typo in "Keys and keyrings" section. Replaces "keying" with
> >   "keyring".
> > - Updates formatting of keyring types.
> > 
> > Signed-off-by: Mayank Gite <drapl0n.kernel@gmail.com>
> 
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
> 
> > ---
> In the future, right here, after that "---" line, it should say
> something like
> 
> v2: use 'git send-email' so that that patch isn't corrupted
> 
> and in the Subject: it should say
> [PATCH v2] ...
> 
> Thanks.
> 
> >  Documentation/security/credentials.rst | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/Documentation/security/credentials.rst b/Documentation/security/credentials.rst
> > index d0191c8b8060..4996838491b1 100644
> > --- a/Documentation/security/credentials.rst
> > +++ b/Documentation/security/credentials.rst
> > @@ -189,9 +189,9 @@ The Linux kernel supports the following types of credentials:
> >       be searched for the desired key.  Each process may subscribe to a number
> >       of keyrings:
> >  
> > -	Per-thread keying
> > -	Per-process keyring
> > -	Per-session keyring
> > +	- Per-thread keyring
> > +	- Per-process keyring
> > +	- Per-session keyring
> >  
> >       When a process accesses a key, if not already present, it will normally be
> >       cached on one of these keyrings for future accesses to find.
> 
> -- 
> ~Randy

Hi,

Thank you for the feedback and acknowledgment. I thought that since my
earlier patch was invalid/corrupted, I should submit a new one rather than
version 2.

I understand the procedure now and will ensure that future revisions follow
the guidelines.

Thanks.

  reply	other threads:[~2026-05-07 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 22:59 [PATCH] Documentation: fix typo and formattting in security/credentials.rst Mayank Gite
2026-05-07  0:36 ` Randy Dunlap
2026-05-07 17:48   ` John Doe [this message]
2026-05-07 18:31     ` Jonathan Corbet
2026-05-07 19:35       ` Mayank Gite
  -- strict thread matches above, loose matches on Subject: below --
2026-05-06  5:49 Mayank Gite
2026-05-06 17:31 ` Randy Dunlap

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=afzQVIv4-Up24VNM@gmail.com \
    --to=drapl0n.kernel@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=rdunlap@infradead.org \
    --cc=sergeh@kernel.org \
    --cc=skhan@linuxfoundation.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