From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rd.dunlab@gmail.com>,
linux1394-devel@lists.sourceforge.net,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
linux-doc@vger.kernel.org, linux-scsi@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v3 0/5] FireWire: clean up kernel-doc, add Documentation chapter
Date: Sat, 15 Sep 2018 16:59:58 +0200 [thread overview]
Message-ID: <20180915165958.3f88a6f8@kant> (raw)
In-Reply-To: <20180906094738.0248c67e@lwn.net>
On Sep 06 Jonathan Corbet wrote:
> On Tue, 4 Sep 2018 17:02:20 -0700
> Randy Dunlap <rd.dunlab@gmail.com> wrote:
> > [PATCH v4 1/5] FireWire: clean up firewire-cdev.h kernel-doc
> > [PATCH v4 2/5] FireWire: clean up core-iso.c kernel-doc
> > [PATCH v4 3/5] FireWire: clean up core-transaction.c kernel-doc
> > [PATCH v4 4/5] FireWire: add a Documentation driver-api chapter
> > [PATCH v4 5/5] FireWire: add driver-api Introduction section
[...]
> > I think that Jon is the best choice to merge this series, but
> > someone please do so. It has already missed 2 merge windows.
>
> I think this is the first time I've received this... Through the
> FireWire maintainer seems like the best path, but it seems that's not
> happening. The patches look good to me, so I've just applied them.
Thanks for taking care of this. I only read superficially through the v1
posting and Takashi Sakamoto's initial responses; sorry to all for not
following up on this then.
--
Stefan Richter
-======---=- =--= -====
http://arcgraph.de/sr/
prev parent reply other threads:[~2018-09-15 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 0:02 [PATCH v3 0/5] FireWire: clean up kernel-doc, add Documentation chapter Randy Dunlap
2018-09-05 0:02 ` [PATCH v4 1/5] FireWire: clean up firewire-cdev.h kernel-doc Randy Dunlap
2018-09-05 0:02 ` [PATCH v4 2/5] FireWire: clean up core-iso.c kernel-doc Randy Dunlap
2018-09-05 0:02 ` [PATCH v4 3/5] FireWire: clean up core-transaction.c kernel-doc Randy Dunlap
2018-09-05 0:02 ` [PATCH v4 4/5] FireWire: add a Documentation driver-api chapter Randy Dunlap
2018-09-05 0:02 ` [PATCH v4 5/5] FireWire: add driver-api Introduction section Randy Dunlap
2018-09-06 15:47 ` [PATCH v3 0/5] FireWire: clean up kernel-doc, add Documentation chapter Jonathan Corbet
2018-09-15 14:59 ` Stefan Richter [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=20180915165958.3f88a6f8@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=martin.petersen@oracle.com \
--cc=o-takashi@sakamocchi.jp \
--cc=rd.dunlab@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).