From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>, linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Eric Biggers <ebiggers@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] Documentation: siphash: formatting fixes
Date: Wed, 20 Apr 2022 03:28:44 -0600 [thread overview]
Message-ID: <87bkww3xyr.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220417075057.127865-1-bagasdotme@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> Formatting fixes for Documentation/security/siphash.rst. The shortlog
> should be self-explanatory. Resend of [1].
>
> [1]: https://lore.kernel.org/linux-doc/20220329042952.10100-1-bagasdotme@gmail.com/
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Eric Biggers <ebiggers@google.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Cc: linux-kernel@vger.kernel.org
>
> Bagas Sanjaya (2):
> Documentation: siphash: convert danger note to warning for HalfSipHash
> Documentation: siphash: enclose HalfSipHash usage example in the
> literal block
>
> Documentation/security/siphash.rst | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2022-04-20 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 7:50 Bagas Sanjaya
2022-04-17 7:50 ` [PATCH RESEND 1/2] Documentation: siphash: convert danger note to warning for HalfSipHash Bagas Sanjaya
2022-04-17 7:50 ` [PATCH RESEND 2/2] Documentation: siphash: enclose HalfSipHash usage example in the literal block Bagas Sanjaya
2022-04-20 9:28 ` Jonathan Corbet [this message]
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=87bkww3xyr.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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
all inboxes | Powered by JetHome®