From: Finn Thain <fthain@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: [PATCH 08/11] Docs/scsi: g_NCR5380: shorten chapter heading
Date: Fri, 19 May 2023 14:45:52 +1000 (AEST) [thread overview]
Message-ID: <5c569351-25c1-1a2b-e506-05f503944656@linux-m68k.org> (raw)
In-Reply-To: <20230518212749.18266-9-rdunlap@infradead.org>
On Thu, 18 May 2023, Randy Dunlap wrote:
> Make the chapter heading be concise yet still descriptive.
> This makes the subsystem table of contents more readable (IMO).
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> Cc: linux-scsi@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Finn Thain <fthain@linux-m68k.org>
> Cc: Michael Schmitz <schmitzmic@gmail.com>
Acked-by: Finn Thain <fthain@linux-m68k.org>
> ---
> Documentation/scsi/g_NCR5380.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff -- a/Documentation/scsi/g_NCR5380.rst b/Documentation/scsi/g_NCR5380.rst
> --- a/Documentation/scsi/g_NCR5380.rst
> +++ b/Documentation/scsi/g_NCR5380.rst
> @@ -1,9 +1,9 @@
> .. SPDX-License-Identifier: GPL-2.0
> .. include:: <isonum.txt>
>
> -==========================================
> -README file for the Linux g_NCR5380 driver
> -==========================================
> +================
> +g_NCR5380 driver
> +================
>
> Copyright |copy| 1993 Drew Eckhard
>
>
next prev parent reply other threads:[~2023-05-19 4:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 21:27 [PATCH 00/11] Documentation/scsi: organize SCSI docs & make more readable Randy Dunlap
2023-05-18 21:27 ` [PATCH 01/11] Docs/scsi: organize the SCSI documentation Randy Dunlap
2023-05-18 21:27 ` [PATCH 02/11] Docs/scsi: introduction: multiple cleanups Randy Dunlap
2023-05-19 4:53 ` Finn Thain
2023-05-18 21:27 ` [PATCH 03/11] Docs/scsi: arcmsr: use a chapter heading for clarity Randy Dunlap
2023-05-18 21:27 ` [PATCH 04/11] Docs/scsi: scsi-changer: shorten the chapter heading Randy Dunlap
2023-05-18 21:27 ` [PATCH 05/11] Docs/scsi: dc395x: " Randy Dunlap
2023-06-01 2:08 ` Bagas Sanjaya
2023-05-18 21:27 ` [PATCH 06/11] Docs/scsi: scsi_fc_transport: fix typo in heading Randy Dunlap
2023-05-18 21:27 ` [PATCH 07/11] Docs/scsi: scsi-generic: multiple cleanups Randy Dunlap
2023-05-18 21:27 ` [PATCH 08/11] Docs/scsi: g_NCR5380: shorten chapter heading Randy Dunlap
2023-05-19 4:45 ` Finn Thain [this message]
2023-05-18 21:27 ` [PATCH 09/11] Docs/scsi: megaraid: clarify " Randy Dunlap
2023-05-18 21:27 ` [PATCH 10/11] Docs/scsi: ncr53c8xx: shorten " Randy Dunlap
2023-05-18 21:27 ` [PATCH 11/11] Docs/scsi: sym53c8xx_2: " Randy Dunlap
2023-05-22 22:38 ` [PATCH 00/11] Documentation/scsi: organize SCSI docs & make more readable Martin K. Petersen
2023-06-01 0:43 ` Martin K. Petersen
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=5c569351-25c1-1a2b-e506-05f503944656@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=corbet@lwn.net \
--cc=jejb@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@infradead.org \
--cc=schmitzmic@gmail.com \
/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
all inboxes | Powered by JetHome®