From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v3 21/23] regulator: dt-bindings: update samsung,s2mpa01.yaml reference
Date: Wed, 20 Oct 2021 07:30:13 +0100 [thread overview]
Message-ID: <20211020073013.6d144c0d@sal.lan> (raw)
In-Reply-To: <YW60a8z0JNDnTLV/@sirena.org.uk>
Em Tue, 19 Oct 2021 13:04:59 +0100
Mark Brown <broonie@kernel.org> escreveu:
> On Tue, Oct 19, 2021 at 09:04:20AM +0100, Mauro Carvalho Chehab wrote:
>
> > To mailbombing on a large number of people, only mailing lists were C/C on the cover.
> > See [PATCH v3 00/23] at: https://lore.kernel.org/all/cover.1634630485.git.mchehab+huawei@kernel.org/
>
> It'd be a bit easier to put a note in here about what the dependencies
> are rather than forcing people to go out to a link to figure out what's
> going on unless it's complicated.
>
> For a case like this where there's no
> dependencies or real relationship between the patches it's probably
> better to just not thread everything and send the patches separately to
> everyone, the threading is just adding noise and confusion.
It is not that easy, unfortunately. On some cases (specially due to
DT binding renames) some patches change the context of a hunk, affecting
a subsequent patch.
I tried a couple of times in the past to send the patches individually,
but that was messier, as there was harder for people to apply them,
as, instead of running b4 just once to get everything, maintainers
would need to apply each patch individually. Also, there were cases
where the patch order would be relevant, due to context changes.
-
Btw, talking about what it would be easier, the best procedure to
adopt is to run:
./scripts/documentation-file-ref-check
Before sending/applying patches touching documents.
That would avoid the need of such fixup patches ;-)
Unfortunately, in the specific case of dt-bindings, things are not
that easy, as doc changes usually go via one tree, while references
to them come from other places.
Regards,
Mauro
next prev parent reply other threads:[~2021-10-20 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 8:03 [PATCH v3 00/23] Fix some issues at documentation Mauro Carvalho Chehab
2021-10-19 8:04 ` [PATCH v3 20/23] dt-bindings: mfd: update x-powers,axp152.yaml reference Mauro Carvalho Chehab
2021-10-19 16:04 ` Chen-Yu Tsai
2021-10-21 12:12 ` Lee Jones
2021-10-19 8:04 ` [PATCH v3 21/23] regulator: dt-bindings: update samsung,s2mpa01.yaml reference Mauro Carvalho Chehab
2021-10-19 8:24 ` Krzysztof Kozlowski
2021-10-19 12:04 ` Mark Brown
2021-10-20 6:30 ` Mauro Carvalho Chehab [this message]
2021-10-20 11:04 ` Mark Brown
2021-10-27 2:59 ` Rob Herring
2021-10-19 8:04 ` [PATCH v3 22/23] regulator: dt-bindings: update samsung,s5m8767.yaml reference Mauro Carvalho Chehab
2021-10-19 8:24 ` Krzysztof Kozlowski
2021-10-19 16:53 ` [PATCH v3 00/23] Fix some issues at documentation Rob Herring
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=20211020073013.6d144c0d@sal.lan \
--to=mchehab+huawei@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@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).