From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [rft, PATCH v1 1/1] gpio: Drop unused inclusions from of_gpio.h
Date: Mon, 13 Mar 2023 22:50:32 +0100 [thread overview]
Message-ID: <CACRpkdY35RkGPp=smaG30JoK+TDXtXH-=DwrtWeXMTT_Brf2zQ@mail.gmail.com> (raw)
In-Reply-To: <20230313144557.35856-1-andriy.shevchenko@linux.intel.com>
On Mon, Mar 13, 2023 at 3:45 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
> As a preliminary step, drop unused inclusions from of_gpio.h,
> so people will use the header only when it's really needed and
> not as a substitute of any of the dropped ones.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>
> For testing purposes on what will fail in CIs. People are also
> encourage to test this, if have time / chance / wish.
Haha the CI gives 6 million errors as usual :D
Wella, just nail them all down, that's how we got rid of
<linux/gpio/driver.h> from <linux/gpio.h> ...
The end result will look really good.
Thanks for looking into this!
Yours,
Linus Walleij
prev parent reply other threads:[~2023-03-13 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 14:45 [rft, PATCH v1 1/1] gpio: Drop unused inclusions from of_gpio.h Andy Shevchenko
2023-03-13 17:16 ` kernel test robot
2023-03-13 17:27 ` kernel test robot
2023-03-13 17:27 ` kernel test robot
2023-03-13 18:08 ` kernel test robot
2023-03-13 18:40 ` kernel test robot
2023-03-13 21:50 ` Linus Walleij [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='CACRpkdY35RkGPp=smaG30JoK+TDXtXH-=DwrtWeXMTT_Brf2zQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=frowand.list@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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 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.