From: Jonathan Corbet <corbet@lwn.net>
To: Otto Sabart <ottosabart@seberm.com>
Cc: linux-doc@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 0/8] Fix bad references to documentation files
Date: Thu, 3 Jan 2019 09:28:49 -0700 [thread overview]
Message-ID: <20190103092849.48e14277@lwn.net> (raw)
In-Reply-To: <cover.1546457946.git.ottosabart@seberm.com>
On Wed, 2 Jan 2019 21:00:47 +0100
Otto Sabart <ottosabart@seberm.com> wrote:
> This series of patches fixes multiple warnings
> from `$ make refcheckdocs` output.
>
> I am still not sure if it's good practise to send these changes in
> a series (because they touch multiple trees) or as a single commit
> because it is one "logical" change :).
Definitely not as a single commit for something like this.
It's a good practice to use the get_maintainer.pl script to figure out who
should receive any given patch. In particular, the various device-tree
patches should go to the device-tree maintainers, the SCSI one to the SCSI
list, etc.
I'll go ahead and apply patch 2 (the ext4 one) since it's a pure docs
fix. For the rest, I'd suggest doing multiple mailings, being sure to get
them to the right maintainers.
Thanks,
jon
prev parent reply other threads:[~2019-01-03 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 20:00 [PATCH 0/8] Fix bad references to documentation files Otto Sabart
2019-01-02 20:01 ` [PATCH 1/8] MAINTAINERS: fix bad file reference into Documentation Otto Sabart
2019-01-02 20:01 ` [PATCH 2/8] doc: filesystems: fix bad references to nonexistent ext4.rst file Otto Sabart
2019-01-02 20:01 ` [PATCH 3/8] doc: bindings: fix bad reference to ARM CPU bindings Otto Sabart
2019-01-03 18:55 ` Otto Sabart
2019-01-03 20:53 ` Rob Herring
2019-01-04 9:26 ` Otto Sabart
2019-01-04 15:52 ` Rob Herring
2019-01-02 20:01 ` [PATCH 4/8] doc: trace: fix reference to cpuidle documentation file Otto Sabart
2019-01-02 20:02 ` [PATCH 5/8] doc: gpio-mvebu: fix broken reference to cp110-system-controller0.txt file Otto Sabart
2019-01-02 20:02 ` [PATCH 6/8] doc: scsi: remove reference to tmscsim.txt file Otto Sabart
2019-01-02 20:02 ` [PATCH 7/8] doc: pinctrl: fix bad reference to pinctrl.txt file Otto Sabart
2019-01-02 20:03 ` [PATCH 8/8] doc: fix multiple broken references Otto Sabart
2019-01-03 16:28 ` Jonathan Corbet [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=20190103092849.48e14277@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=ottosabart@seberm.com \
--cc=trivial@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 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.