All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rd.dunlab@gmail.com>
To: linux1394-devel@lists.sourceforge.net
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	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>,
	Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH v3 0/5] FireWire: clean up kernel-doc, add Documentation chapter
Date: Tue,  4 Sep 2018 17:02:20 -0700	[thread overview]
Message-ID: <20180905000225.10733-1-rd.dunlab@gmail.com> (raw)

This patch series cleans up kernel-doc warnings in several
FireWire source files and then adds a Documentation driver-api
chapter for FireWire.

[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

The only changes in v4 are (a) respin against current -next and
(b) add more Cc:s so that someone will please merge the series.(*)

I think that Jon is the best choice to merge this series, but
someone please do so.  It has already missed 2 merge windows.

(*): Stefan hasn't replied to patches in the linux1394-devel
mailing list recently.  E.g., see:
https://sourceforge.net/p/linux1394/mailman/message/36406886/

 Documentation/driver-api/firewire.rst |   50 +++++++++++++++++++++++-
 Documentation/driver-api/index.rst    |    1 
 drivers/firewire/core-iso.c           |    7 +++
 drivers/firewire/core-transaction.c   |   10 ++++
 include/uapi/linux/firewire-cdev.h    |   22 ++++++----
 5 files changed, 81 insertions(+), 9 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rd.dunlab@gmail.com>
To: linux1394-devel@lists.sourceforge.net
Cc: Jonathan Corbet <corbet@lwn.net>,
	"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, linux-doc@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v3 0/5] FireWire: clean up kernel-doc, add Documentation chapter
Date: Tue,  4 Sep 2018 17:02:20 -0700	[thread overview]
Message-ID: <20180905000225.10733-1-rd.dunlab@gmail.com> (raw)

This patch series cleans up kernel-doc warnings in several
FireWire source files and then adds a Documentation driver-api
chapter for FireWire.

[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

The only changes in v4 are (a) respin against current -next and
(b) add more Cc:s so that someone will please merge the series.(*)

I think that Jon is the best choice to merge this series, but
someone please do so.  It has already missed 2 merge windows.

(*): Stefan hasn't replied to patches in the linux1394-devel
mailing list recently.  E.g., see:
https://sourceforge.net/p/linux1394/mailman/message/36406886/

 Documentation/driver-api/firewire.rst |   50 +++++++++++++++++++++++-
 Documentation/driver-api/index.rst    |    1 
 drivers/firewire/core-iso.c           |    7 +++
 drivers/firewire/core-transaction.c   |   10 ++++
 include/uapi/linux/firewire-cdev.h    |   22 ++++++----
 5 files changed, 81 insertions(+), 9 deletions(-)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

             reply	other threads:[~2018-09-05  0:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05  0:02 Randy Dunlap [this message]
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   ` 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   ` 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   ` 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   ` Randy Dunlap
2018-09-05  0:02 ` [PATCH v4 5/5] FireWire: add driver-api Introduction section Randy Dunlap
2018-09-05  0:02   ` Randy Dunlap
2018-09-06 15:47 ` [PATCH v3 0/5] FireWire: clean up kernel-doc, add Documentation chapter Jonathan Corbet
2018-09-06 15:47   ` Jonathan Corbet
2018-09-15 14:59   ` Stefan Richter
2018-09-15 14:59     ` Stefan Richter

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=20180905000225.10733-1-rd.dunlab@gmail.com \
    --to=rd.dunlab@gmail.com \
    --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=rdunlap@infradead.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.