From: Kees Cook <keescook@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Dragan Cvetic <draganc@xilinx.com>,
Derek Kiernan <dkiernan@xilinx.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] docs: misc: xilinx_sdfec: Actually add documentation
Date: Fri, 11 Oct 2019 09:16:58 -0700 [thread overview]
Message-ID: <201910110916.2DC522EA@keescook> (raw)
In-Reply-To: <20191011100223.6f3eff7e@lwn.net>
On Fri, Oct 11, 2019 at 10:02:23AM -0600, Jonathan Corbet wrote:
> On Fri, 11 Oct 2019 08:59:22 +0000
> Dragan Cvetic <draganc@xilinx.com> wrote:
>
> > Yes, please add the file.
>
> OK, I've applied the patch, thanks. I took the liberty of sticking on a
> final newline while I was at it.
Yay! Thank you! :)
--
Kees Cook
prev parent reply other threads:[~2019-10-11 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 17:03 [PATCH] docs: misc: xilinx_sdfec: Actually add documentation Kees Cook
2019-10-10 22:35 ` Kees Cook
2019-10-10 22:38 ` Randy Dunlap
2019-10-10 23:29 ` Kees Cook
2019-10-10 22:39 ` Jonathan Corbet
2019-10-11 8:59 ` Dragan Cvetic
2019-10-11 16:02 ` Jonathan Corbet
2019-10-11 16:16 ` Kees Cook [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=201910110916.2DC522EA@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=dkiernan@xilinx.com \
--cc=draganc@xilinx.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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).