From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "J. Neuschäfer" <j.ne@posteo.net>,
openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 1/1] pinctrl: wpcm450: Switch to use for_each_gpiochip_node() helper
Date: Wed, 26 Feb 2025 16:22:58 +0200 [thread overview]
Message-ID: <Z78jwi8s34t3H8fG@smile.fi.intel.com> (raw)
In-Reply-To: <20250220155036.2734838-1-andriy.shevchenko@linux.intel.com>
On Thu, Feb 20, 2025 at 05:50:11PM +0200, Andy Shevchenko wrote:
> Switch the code to use for_each_gpiochip_node() helper.
>
> While at it, correct header inclusion as device property APIs
> are provided in property.h.
Linus, Are you okay with the change?
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "J. Neuschäfer" <j.ne@posteo.net>,
openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [PATCH v2 1/1] pinctrl: wpcm450: Switch to use for_each_gpiochip_node() helper
Date: Wed, 26 Feb 2025 16:22:58 +0200 [thread overview]
Message-ID: <Z78jwi8s34t3H8fG@smile.fi.intel.com> (raw)
In-Reply-To: <20250220155036.2734838-1-andriy.shevchenko@linux.intel.com>
On Thu, Feb 20, 2025 at 05:50:11PM +0200, Andy Shevchenko wrote:
> Switch the code to use for_each_gpiochip_node() helper.
>
> While at it, correct header inclusion as device property APIs
> are provided in property.h.
Linus, Are you okay with the change?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-26 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 15:50 [PATCH v2 1/1] pinctrl: wpcm450: Switch to use for_each_gpiochip_node() helper Andy Shevchenko
2025-02-20 15:50 ` Andy Shevchenko
2025-02-26 14:22 ` Andy Shevchenko [this message]
2025-02-26 14:22 ` Andy Shevchenko
2025-02-27 23:30 ` Linus Walleij
2025-02-27 23:30 ` 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=Z78jwi8s34t3H8fG@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=j.ne@posteo.net \
--cc=j.neuschaefer@gmx.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@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 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.