linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org
Subject: [36/57] docs: usb: convert documents to ReST
Date: Tue, 16 Apr 2019 08:43:28 -0300	[thread overview]
Message-ID: <20190416084328.380de91e@coco.lan> (raw)

Em Tue, 16 Apr 2019 09:12:32 +0300
Felipe Balbi <felipe.balbi@linux.intel.com> escreveu:

> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> writes:
> 
> > Convert USB documents to ReST, in order to prepare for adding it
> > to the kernel API book, as most of the stuff there are driver or
> > subsystem-related.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > ---
> >  Documentation/usb/WUSB-Design-overview.txt |  56 +-
> >  Documentation/usb/acm.txt                  | 156 +++---
> >  Documentation/usb/authorization.txt        |  75 +--
> >  Documentation/usb/chipidea.txt             | 101 ++--
> >  Documentation/usb/dwc3.txt                 |  12 +-
> >  Documentation/usb/ehci.txt                 |  42 +-
> >  Documentation/usb/functionfs.txt           |  17 +-
> >  Documentation/usb/gadget-testing.txt       | 609 ++++++++++++---------
> >  Documentation/usb/gadget_configfs.txt      | 302 +++++-----
> >  Documentation/usb/gadget_hid.txt           | 175 +++---
> >  Documentation/usb/gadget_multi.txt         |  43 +-
> >  Documentation/usb/gadget_printer.txt       | 155 +++---
> >  Documentation/usb/gadget_serial.txt        |  73 +--
> >  Documentation/usb/iuu_phoenix.txt          |  34 +-
> >  Documentation/usb/mass-storage.txt         |  19 +-
> >  Documentation/usb/misc_usbsevseg.txt       |   9 +-
> >  Documentation/usb/mtouchusb.txt            |  42 +-
> >  Documentation/usb/ohci.txt                 |   5 +-
> >  Documentation/usb/rio.txt                  |  83 +--
> >  Documentation/usb/usb-help.txt             |  21 +-
> >  Documentation/usb/usb-serial.txt           | 203 ++++---
> >  Documentation/usb/usbip_protocol.txt       | 552 ++++++++++---------
> >  Documentation/usb/usbmon.txt               | 100 ++--  
> 
> should you change extension to .rst while at that?

I did that on a first version (not submitted):

	https://git.linuxtv.org/mchehab/experimental.git/commit/?h=all_with_indexes&id=d7eec4678dbfeb1a40c58bca7a157c8a4c39fa04

but I opted do the postpone the rename to a new series yet to be
sent.

The problem is that renaming it will make Sphinx to try to build them,
causing lots of warnings because they won't be inside an index file.
Adding index would touch Documentation/index (or Documentation/drivers-api),
with would cause merge conflicts.

Once this patch gets merged upstream, a renaming patch can happen
anytime. It probably makes sense to do all renames at once, late
at a merge window.


Thanks,
Mauro

WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH 36/57] docs: usb: convert documents to ReST
Date: Tue, 16 Apr 2019 08:43:28 -0300	[thread overview]
Message-ID: <20190416084328.380de91e@coco.lan> (raw)
Message-ID: <20190416114328.c6JrDX_WLCRoNDy2L4BvM6phtBXafsxvfQ5MLcf_5C8@z> (raw)
In-Reply-To: <874l6ya373.fsf@linux.intel.com>

Em Tue, 16 Apr 2019 09:12:32 +0300
Felipe Balbi <felipe.balbi@linux.intel.com> escreveu:

> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> writes:
> 
> > Convert USB documents to ReST, in order to prepare for adding it
> > to the kernel API book, as most of the stuff there are driver or
> > subsystem-related.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > ---
> >  Documentation/usb/WUSB-Design-overview.txt |  56 +-
> >  Documentation/usb/acm.txt                  | 156 +++---
> >  Documentation/usb/authorization.txt        |  75 +--
> >  Documentation/usb/chipidea.txt             | 101 ++--
> >  Documentation/usb/dwc3.txt                 |  12 +-
> >  Documentation/usb/ehci.txt                 |  42 +-
> >  Documentation/usb/functionfs.txt           |  17 +-
> >  Documentation/usb/gadget-testing.txt       | 609 ++++++++++++---------
> >  Documentation/usb/gadget_configfs.txt      | 302 +++++-----
> >  Documentation/usb/gadget_hid.txt           | 175 +++---
> >  Documentation/usb/gadget_multi.txt         |  43 +-
> >  Documentation/usb/gadget_printer.txt       | 155 +++---
> >  Documentation/usb/gadget_serial.txt        |  73 +--
> >  Documentation/usb/iuu_phoenix.txt          |  34 +-
> >  Documentation/usb/mass-storage.txt         |  19 +-
> >  Documentation/usb/misc_usbsevseg.txt       |   9 +-
> >  Documentation/usb/mtouchusb.txt            |  42 +-
> >  Documentation/usb/ohci.txt                 |   5 +-
> >  Documentation/usb/rio.txt                  |  83 +--
> >  Documentation/usb/usb-help.txt             |  21 +-
> >  Documentation/usb/usb-serial.txt           | 203 ++++---
> >  Documentation/usb/usbip_protocol.txt       | 552 ++++++++++---------
> >  Documentation/usb/usbmon.txt               | 100 ++--  
> 
> should you change extension to .rst while at that?

I did that on a first version (not submitted):

	https://git.linuxtv.org/mchehab/experimental.git/commit/?h=all_with_indexes&id=d7eec4678dbfeb1a40c58bca7a157c8a4c39fa04

but I opted do the postpone the rename to a new series yet to be
sent.

The problem is that renaming it will make Sphinx to try to build them,
causing lots of warnings because they won't be inside an index file.
Adding index would touch Documentation/index (or Documentation/drivers-api),
with would cause merge conflicts.

Once this patch gets merged upstream, a renaming patch can happen
anytime. It probably makes sense to do all renames at once, late
at a merge window.


Thanks,
Mauro

         reply	other threads:[~2019-04-16 11:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  2:55 [PATCH 00/57] Convert files to ReST Mauro Carvalho Chehab
2019-04-16  2:56 ` [36/57] docs: usb: convert documents " Mauro Carvalho Chehab
2019-04-16  2:56   ` [PATCH 36/57] " Mauro Carvalho Chehab
2019-04-16  6:12   ` [36/57] " Felipe Balbi
2019-04-16  6:12     ` [PATCH 36/57] " Felipe Balbi
2019-04-16 11:43     ` Mauro Carvalho Chehab [this message]
2019-04-16 11:43       ` Mauro Carvalho Chehab
2019-04-18 12:42 ` Avoiding merge conflicts while adding new docs - Was: Re: [PATCH 00/57] Convert files " Mauro Carvalho Chehab
2019-04-19 22:10   ` Jonathan Corbet

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=20190416084328.380de91e@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=corbet@lwn.net \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@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).