linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org
Cc: nvdimm@lists.linux.dev, linux-doc@vger.kernel.org,
	Song Liu <song@kernel.org>,
	dm-devel@redhat.com, netdev@vger.kernel.org,
	Zefan Li <lizefan.x@bytedance.com>,
	sparclinux@vger.kernel.org,
	Neeraj Upadhyay <quic_neeraju@quicinc.com>,
	Alasdair Kergon <agk@redhat.com>,
	Dave Jiang <dave.jiang@intel.com>,
	linux-scsi@vger.kernel.org,
	Vishal Verma <vishal.l.verma@intel.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-media@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Mike Snitzer <snitzer@kernel.org>,
	Josh Triplett <josh@joshtriplett.org>,
	linux-raid@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	Jiri Pirko <jiri@nvidia.com>,
	cgroups@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-hwmon@vger.kernel.org, rcu@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-mm@kvack.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	Vinod Koul <vkoul@kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	dmaengine@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [dm-devel] [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
Date: Thu, 2 Feb 2023 10:39:02 -0800	[thread overview]
Message-ID: <8540c721-6bb9-3542-d9bd-940b59d3a7a4@acm.org> (raw)
In-Reply-To: <a2c560bb-3b5c-ca56-c5c2-93081999281d@infradead.org>

On 2/2/23 10:33, Randy Dunlap wrote:
> On 2/2/23 10:09, Jonathan Corbet wrote:
>> Randy Dunlap <rdunlap@infradead.org> writes:
>>>   [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
>>>   [PATCH 7/9] Documentation: scsi: correct spelling
>>
>> I've left these for the SCSI folks for now.  Do we *really* want to be
>> fixing spelling in ChangeLog files from almost 20 years ago?
> 
> That's why I made it a separate patch -- so the SCSI folks can decide that...

How about removing the Documentation/scsi/ChangeLog.* files? I'm not 
sure these changelogs are still useful since these duplicate information 
that is already available in the output of git log ${driver_directory}.

Thanks,

Bart.



  reply	other threads:[~2023-02-02 18:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
2023-01-30  9:35   ` Mukesh Ojha
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
2023-01-30 19:11   ` Dan Williams
2023-01-30 19:45   ` Song Liu
2023-01-31  9:10   ` Greg Kroah-Hartman
2023-01-29 23:10 ` [PATCH 3/9] Documentation: hwmon: " Randy Dunlap
2023-01-30  0:39   ` Guenter Roeck
2023-01-29 23:10 ` [PATCH 4/9] Documentation: networking: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 5/9] Documentation: RCU: " Randy Dunlap
2023-01-30  5:24   ` Paul E. McKenney
2023-01-29 23:10 ` [PATCH 6/9] Documentation: scsi/ChangeLog*: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 7/9] Documentation: scsi: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 8/9] Documentation: sparc: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 9/9] Documentation: userspace-api: " Randy Dunlap
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
2023-01-31 12:17   ` Paolo Abeni
2023-02-02 18:09 ` Jonathan Corbet
2023-02-02 18:33   ` Randy Dunlap
2023-02-02 18:39     ` Bart Van Assche [this message]
2023-02-02 18:46       ` [dm-devel] " Jonathan Corbet
2023-02-02 18:54         ` James Bottomley
2023-02-14 16:57 ` (subset) " 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=8540c721-6bb9-3542-d9bd-940b59d3a7a4@acm.org \
    --to=bvanassche@acm.org \
    --cc=agk@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=dm-devel@redhat.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=frederic@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=jdelvare@suse.com \
    --cc=jejb@linux.ibm.com \
    --cc=jiri@nvidia.com \
    --cc=josh@joshtriplett.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lizefan.x@bytedance.com \
    --cc=martin.petersen@oracle.com \
    --cc=mchehab@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=quic_neeraju@quicinc.com \
    --cc=rcu@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=vishal.l.verma@intel.com \
    --cc=vkoul@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 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).