From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] PCI/pwrctl: pwrseq: don't use OF-specific routines
Date: Fri, 4 Oct 2024 17:00:39 -0500 [thread overview]
Message-ID: <20241004220039.GA363598@bhelgaas> (raw)
In-Reply-To: <20241004125821.47525-1-brgl@bgdev.pl>
On Fri, Oct 04, 2024 at 02:58:21PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> This driver doesn't need to use OF interfaces directly. Replace the
> single usage of an of_ function and replace it with a generic device
> property variant. Drop the of.h header and pull in property.h instead.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Applied to pci/pwrseq for v6.13, thanks.
> ---
> Bjorn: This may conflict with [1] but this should go for v6.13 while [1]
> is a fix that's targetting v6.12. If git doesn't figure it out then the
> resolution is trivial, just add <linux/property.h> in both and drop
> <linux/of.h>.
>
> [1] https://lore.kernel.org/linux-pci/20241004125227.46514-1-brgl@bgdev.pl/
>
> drivers/pci/pwrctl/pci-pwrctl-pwrseq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pwrctl/pci-pwrctl-pwrseq.c b/drivers/pci/pwrctl/pci-pwrctl-pwrseq.c
> index a23a4312574b..d3f960612cf3 100644
> --- a/drivers/pci/pwrctl/pci-pwrctl-pwrseq.c
> +++ b/drivers/pci/pwrctl/pci-pwrctl-pwrseq.c
> @@ -6,9 +6,9 @@
> #include <linux/device.h>
> #include <linux/mod_devicetable.h>
> #include <linux/module.h>
> -#include <linux/of.h>
> #include <linux/pci-pwrctl.h>
> #include <linux/platform_device.h>
> +#include <linux/property.h>
> #include <linux/pwrseq/consumer.h>
> #include <linux/slab.h>
> #include <linux/types.h>
> @@ -35,7 +35,7 @@ static int pci_pwrctl_pwrseq_probe(struct platform_device *pdev)
> if (!data)
> return -ENOMEM;
>
> - data->pwrseq = devm_pwrseq_get(dev, of_device_get_match_data(dev));
> + data->pwrseq = devm_pwrseq_get(dev, device_get_match_data(dev));
> if (IS_ERR(data->pwrseq))
> return dev_err_probe(dev, PTR_ERR(data->pwrseq),
> "Failed to get the power sequencer\n");
> --
> 2.43.0
>
prev parent reply other threads:[~2024-10-04 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 12:58 [PATCH] PCI/pwrctl: pwrseq: don't use OF-specific routines Bartosz Golaszewski
2024-10-04 22:00 ` Bjorn Helgaas [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=20241004220039.GA363598@bhelgaas \
--to=helgaas@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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).