From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
Sascha Hauer <sha@pengutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
bartosz.golaszewski@linaro.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
Marco Felsch <m.felsch@pengutronix.de>,
christophe.leroy@csgroup.eu, linux-gpio@vger.kernel.org,
kernel@pengutronix.de, shawnguo@kernel.org
Subject: Re: GPIO static allocation warning with v6.2-rcX
Date: Thu, 2 Mar 2023 17:40:29 +0200 [thread overview]
Message-ID: <ZADDbYYWdSiXozgm@smile.fi.intel.com> (raw)
In-Reply-To: <ZAAHlyjr+pNHTMoo@sol>
On Thu, Mar 02, 2023 at 10:19:03AM +0800, Kent Gibson wrote:
> I didn't respond to this earlier, as I considered it best to let the
> thread die and not inflame the issue.
>
> Adding Andy as he raised the issue again in another thread.
Thank you, Kent, it is helpful.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-03-02 15:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:46 GPIO static allocation warning with v6.2-rcX Marco Felsch
2023-01-23 14:55 ` Bartosz Golaszewski
2023-01-23 14:56 ` Bartosz Golaszewski
2023-01-25 9:35 ` Sascha Hauer
2023-01-25 13:56 ` Bartosz Golaszewski
2023-01-26 10:27 ` Sascha Hauer
2023-01-26 1:57 ` Kent Gibson
2023-01-26 10:14 ` Sascha Hauer
2023-01-26 10:26 ` Kent Gibson
2023-01-26 9:35 ` Linus Walleij
2023-01-26 10:49 ` Sascha Hauer
2023-01-29 18:33 ` Robert Schwebel
2023-01-30 10:19 ` Linus Walleij
2023-01-30 11:02 ` Marco Felsch
2023-01-30 15:01 ` Linus Walleij
2023-01-30 15:45 ` Rob Herring
2023-01-31 7:21 ` Alexander Stein
2023-01-30 17:26 ` Andy Shevchenko
2023-01-30 16:48 ` Uwe Kleine-König
2023-01-30 17:21 ` Bartosz Golaszewski
2023-01-30 23:26 ` Linus Walleij
2023-03-02 2:19 ` Kent Gibson
2023-03-02 15:40 ` Andy Shevchenko [this message]
2023-01-26 9:42 ` Linus Walleij
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=ZADDbYYWdSiXozgm@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=christophe.leroy@csgroup.eu \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
--cc=sha@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=warthog618@gmail.com \
/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.