From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: Derek Kiernan <derek.kiernan@xilinx.com>,
Dragan Cvetic <dragan.cvetic@xilinx.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: misc: xilinx_sdfec: Actually add documentation
Date: Thu, 10 Oct 2019 16:39:05 -0600 [thread overview]
Message-ID: <20191010163905.70a4d6e1@lwn.net> (raw)
In-Reply-To: <201910101535.1804FC6@keescook>
On Thu, 10 Oct 2019 15:35:41 -0700
Kees Cook <keescook@chromium.org> wrote:
> On Wed, Oct 02, 2019 at 10:03:55AM -0700, Kees Cook wrote:
> > From: Derek Kiernan <derek.kiernan@xilinx.com>
> >
> > Add SD-FEC driver documentation.
> >
> > Signed-off-by: Derek Kiernan <derek.kiernan@xilinx.com>
> > Signed-off-by: Dragan Cvetic <dragan.cvetic@xilinx.com>
> > Link: https://lore.kernel.org/r/1560274185-264438-11-git-send-email-dragan.cvetic@xilinx.com
> > [kees: extracted from v7 as it was missing in the commit for v8]
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> > ---
> > As mentioned[1], this file went missing and causes a warning in ReST
> > parsing, so I've extracted the patch and am sending it directly to Jon.
> > [1] https://lore.kernel.org/lkml/201909231450.4C6CF32@keescook/
> > ---
>
> friendly ping! :)
>
> -Kees
It's sitting in my queue. I was hoping to hear from Derek that it was OK
to add...Derek are you out there?
Thanks,
jon
next prev parent reply other threads:[~2019-10-10 22:39 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 [this message]
2019-10-11 8:59 ` Dragan Cvetic
2019-10-11 16:02 ` Jonathan Corbet
2019-10-11 16:16 ` Kees Cook
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=20191010163905.70a4d6e1@lwn.net \
--to=corbet@lwn.net \
--cc=derek.kiernan@xilinx.com \
--cc=dragan.cvetic@xilinx.com \
--cc=keescook@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.