From: Christopher Li <sparse@chrisli.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: [PATCH] Documentation: editing fixes in test-suite
Date: Tue, 23 Jan 2018 02:59:02 -0800 [thread overview]
Message-ID: <CANeU7Qk+31+bOCcnbMi7oYCLPur1+of1a8YEKtjHJ2ievwpGsg@mail.gmail.com> (raw)
In-Reply-To: <5bf3731a-c3be-e94e-2aaf-4c443e6ed870@infradead.org>
On Sun, Jan 21, 2018 at 9:38 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix typos, grammar, punctuation, and spelling in Documentation/test-suite.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> Cc: Josh Triplett <josh@joshtriplett.org>
Thank you. Applied in master.
Chris
prev parent reply other threads:[~2018-01-23 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 5:38 [PATCH] Documentation: editing fixes in test-suite Randy Dunlap
2018-01-22 5:48 ` Luc Van Oostenryck
2018-01-22 15:31 ` Josh Triplett
2018-01-23 10:59 ` Christopher Li [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=CANeU7Qk+31+bOCcnbMi7oYCLPur1+of1a8YEKtjHJ2ievwpGsg@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).