From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <shuah@kernel.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: dev-tools: kselftest.rst: update config file location
Date: Fri, 31 Aug 2018 16:26:36 -0600 [thread overview]
Message-ID: <20180831162636.791d4146@lwn.net> (raw)
In-Reply-To: <55c84596-0e12-0211-dbee-9eddb9a0ab28@kernel.org>
On Mon, 27 Aug 2018 11:57:58 -0600
Shuah Khan <shuah@kernel.org> wrote:
> Jo Jon,
>
> This patch looks good. Here is my Ack for it go through doc tree.
>
> Acked-by: Shuah Khan (Samsung OSG) <shuah@kernel.org>
Applied, thanks.
jon
prev parent reply other threads:[~2018-08-31 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 12:47 [PATCH] doc: dev-tools: kselftest.rst: update config file location Anders Roxell
2018-08-27 17:57 ` Shuah Khan
2018-08-31 22:26 ` 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=20180831162636.791d4146@lwn.net \
--to=corbet@lwn.net \
--cc=anders.roxell@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).