Em Tue, 19 Oct 2021 13:04:59 +0100 Mark Brown <broonie@xxxxxxxxxx> 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@xxxxxxxxxx/ > > 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
