From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [rft, PATCH v2 00/36] pinctrl: Clean up and add missed headers
Date: Tue, 11 Oct 2022 13:56:09 -0700 [thread overview]
Message-ID: <0684f480-2092-d520-2c8e-bd9a2dca47e3@gmail.com> (raw)
In-Reply-To: <20221010201453.77401-1-andriy.shevchenko@linux.intel.com>
On 10/10/2022 1:14 PM, Andy Shevchenko wrote:
> Currently the header inclusion inside the pinctrl headers seems more arbitrary
> than logical. This series is basically out of two parts:
> - add missed headers to the pin control drivers / users
> - clean up the headers of pin control subsystem
>
> The idea is to have this series to be pulled after -rc1 by the GPIO and
> pin control subsystems, so all new drivers will utilize cleaned up headers
> of the pin control.
>
> Please, review and comment.
Did you really need to split this on a per-driver basis as opposed to
just a treewide drivers/pinctrl, drivers/media and drivers/gpiolib patch
set?
36 patches seems needlessly high when 4 patches could have achieve the
same outcome.
--
Florian
next prev parent reply other threads:[~2022-10-11 20:56 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 20:14 [rft, PATCH v2 00/36] pinctrl: Clean up and add missed headers Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 01/36] gpiolib: tegra186: Add missed header(s) Andy Shevchenko
2022-10-17 8:52 ` Linus Walleij
2022-10-17 9:35 ` Bartosz Golaszewski
2022-10-17 12:15 ` Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 02/36] gpiolib: cdev: " Andy Shevchenko
2022-10-11 0:01 ` Kent Gibson
2022-10-11 8:05 ` Andy Shevchenko
2022-10-11 13:48 ` Andy Shevchenko
2022-10-11 14:13 ` Kent Gibson
2022-10-11 14:28 ` Andy Shevchenko
2022-10-11 14:39 ` Geert Uytterhoeven
2022-10-11 15:19 ` Andy Shevchenko
2022-10-11 15:44 ` Andy Shevchenko
2022-10-12 13:30 ` Andy Shevchenko
2022-10-12 13:54 ` Kent Gibson
2022-10-10 20:14 ` [PATCH v2 03/36] media: c8sectpfe: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 04/36] pinctrl: actions: " Andy Shevchenko
2022-10-17 8:55 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 05/36] pinctrl: aspeed: " Andy Shevchenko
2022-10-17 8:55 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 06/36] pinctrl: at91: " Andy Shevchenko
2022-10-12 7:52 ` Claudiu.Beznea
2022-10-17 8:56 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 07/36] pinctrl: axp209: " Andy Shevchenko
2022-10-11 16:14 ` Chen-Yu Tsai
2022-10-17 8:57 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 08/36] pinctrl: bcm: " Andy Shevchenko
2022-10-17 8:58 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 09/36] pinctrl: cygnus-mux: " Andy Shevchenko
2022-10-17 8:59 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 10/36] pinctrl: imx: " Andy Shevchenko
2022-10-17 8:59 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 11/36] pinctrl: ingenic: " Andy Shevchenko
2022-10-12 9:15 ` Paul Cercueil
2022-10-17 9:00 ` Linus Walleij
2022-10-10 20:14 ` [PATCH v2 12/36] pinctrl: k210: " Andy Shevchenko
2022-10-10 22:33 ` Damien Le Moal
2022-10-11 7:58 ` Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 13/36] pinctrl: lochnagar: " Andy Shevchenko
2022-10-11 9:03 ` Charles Keepax
2022-10-10 20:14 ` [PATCH v2 14/36] pinctrl: mediatek: " Andy Shevchenko
2022-10-11 14:49 ` AngeloGioacchino Del Regno
2022-10-10 20:14 ` [PATCH v2 15/36] pinctrl: mvebu: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 16/36] pinctrl: npcm7xx: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 17/36] pinctrl: ocelot: " Andy Shevchenko
2022-10-11 9:52 ` Horatiu Vultur
2022-10-10 20:14 ` [PATCH v2 18/36] pinctrl: qcom: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 19/36] pinctrl: renesas: " Andy Shevchenko
2022-10-11 8:10 ` Geert Uytterhoeven
2022-10-10 20:14 ` [PATCH v2 20/36] pinctrl: samsung: " Andy Shevchenko
2022-10-11 16:05 ` Krzysztof Kozlowski
2022-10-10 20:14 ` [PATCH v2 21/36] pinctrl: single: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 22/36] pinctrl: spear: " Andy Shevchenko
2022-10-11 2:56 ` Viresh Kumar
2022-10-10 20:14 ` [PATCH v2 23/36] pinctrl: sprd: " Andy Shevchenko
2022-10-13 1:23 ` Baolin Wang
2022-10-10 20:14 ` [PATCH v2 24/36] pinctrl: st: " Andy Shevchenko
2022-10-11 6:16 ` Patrice CHOTARD
2022-10-10 20:14 ` [PATCH v2 25/36] pinctrl: starfive: " Andy Shevchenko
2022-10-11 8:31 ` Emil Renner Berthing
2022-10-11 9:06 ` Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 26/36] pinctrl: stm32: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 27/36] pinctrl: stmfx: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 28/36] pinctrl: tegra: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 29/36] pinctrl: ti-iodelay: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 30/36] pinctrl: uniphier: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 31/36] pinctrl: zynqmp: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 32/36] pinctrl: cherryview: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 33/36] pinctrl: lynxpoint: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 34/36] pinctrl: merrifield: " Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 35/36] pinctrl: intel: " Andy Shevchenko
2022-10-13 14:53 ` Mika Westerberg
2022-10-13 16:05 ` Andy Shevchenko
2022-10-10 20:14 ` [PATCH v2 36/36] pinctrl: Clean up headers Andy Shevchenko
2022-10-11 7:30 ` Basavaraj Natikar
2022-10-11 8:46 ` Geert Uytterhoeven
2022-10-11 9:07 ` Andy Shevchenko
2022-10-18 13:04 ` Geert Uytterhoeven
2022-10-18 13:07 ` Andy Shevchenko
2022-10-11 9:04 ` Andy Shevchenko
2022-10-11 7:10 ` [rft, PATCH v2 00/36] pinctrl: Clean up and add missed headers Bartosz Golaszewski
2022-10-11 9:02 ` Andy Shevchenko
2022-10-11 20:56 ` Florian Fainelli [this message]
2022-10-12 10:04 ` Andy Shevchenko
2022-10-14 15:11 ` Andy Shevchenko
2022-10-17 9:02 ` Linus Walleij
2022-10-17 9:27 ` Andy Shevchenko
2022-10-17 9:58 ` Linus Walleij
2022-10-17 12:18 ` Andy Shevchenko
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=0684f480-2092-d520-2c8e-bd9a2dca47e3@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-aspeed@lists.ozlabs.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).