From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel@gpiccoli.net,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] Documentation: Fix duplicate statement about raw_spinlock_t type
Date: Fri, 25 Mar 2022 16:38:33 -0300 [thread overview]
Message-ID: <34e5d700-7ff4-666f-9404-1fe3fe1abc7f@igalia.com> (raw)
In-Reply-To: <87r16peslf.fsf@meer.lwn.net>
On 25/03/2022 16:32, Jonathan Corbet wrote:
> "Guilherme G. Piccoli" <gpiccoli@igalia.com> writes:
> [...]
> For future reference, a far better changelog would have been something
> like:
>
> Remove the duplicated sentence from locktypes.rst
>
> Thanks,
>
> jon
Thanks Jon, and feel free to change that when applying in case you
prefer, it's a good choice of words, better than mine.
Cheers,
Guilherme
prev parent reply other threads:[~2022-03-25 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:41 [PATCH] Documentation: Fix duplicate statement about raw_spinlock_t type Guilherme G. Piccoli
2022-03-25 19:32 ` Jonathan Corbet
2022-03-25 19:38 ` Guilherme G. Piccoli [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=34e5d700-7ff4-666f-9404-1fe3fe1abc7f@igalia.com \
--to=gpiccoli@igalia.com \
--cc=corbet@lwn.net \
--cc=kernel@gpiccoli.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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