From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Peter Rosin <peda@axentia.se>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, kernel test robot <lkp@intel.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH 3/3] gpiolib: add gpio_device_get_label() stub for !GPIOLIB
Date: Thu, 25 Jan 2024 10:14:39 +0100 [thread overview]
Message-ID: <0039e8e3-bfb7-43af-ab04-53aeaa02f4b0@linaro.org> (raw)
In-Reply-To: <CAMRc=MfYg5MgndDZtrAaScmtjXm4-AX6y1np7V3p4ngBKZG-pw@mail.gmail.com>
On 25/01/2024 10:04, Bartosz Golaszewski wrote:
> On Thu, Jan 25, 2024 at 9:16 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> Add empty stub of gpio_device_get_label() when GPIOLIB is not enabled.
>>
>> Cc: <stable@vger.kernel.org>
>> Fixes: d1f7728259ef ("gpiolib: provide gpio_device_get_label()")
>> Suggested-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
>>
>> Cc: Philipp Zabel <p.zabel@pengutronix.de>
>>
>> Reset framework will need it:
>> https://lore.kernel.org/oe-kbuild-all/202401250958.YksQmnWj-lkp@intel.com/
>
> And I suppose you'll want an immutable branch for that?
I guess that's the question to Philipp, but other way could be an Ack.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-25 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 8:15 [PATCH 1/3] gpiolib: add gpiod_to_gpio_device() stub for !GPIOLIB Krzysztof Kozlowski
2024-01-25 8:16 ` [PATCH 2/3] gpiolib: add gpio_device_get_base() " Krzysztof Kozlowski
2024-01-25 8:16 ` [PATCH 3/3] gpiolib: add gpio_device_get_label() " Krzysztof Kozlowski
2024-01-25 9:04 ` Bartosz Golaszewski
2024-01-25 9:14 ` Krzysztof Kozlowski [this message]
2024-01-25 9:28 ` Bartosz Golaszewski
2024-01-25 9:34 ` Philipp Zabel
2024-01-25 8:36 ` [PATCH 1/3] gpiolib: add gpiod_to_gpio_device() " Bartosz Golaszewski
2024-01-25 8:59 ` Krzysztof Kozlowski
2024-01-31 9:00 ` 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=0039e8e3-bfb7-43af-ab04-53aeaa02f4b0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=p.zabel@pengutronix.de \
--cc=peda@axentia.se \
--cc=stable@vger.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 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).