From: Stefan Wahren <stefan.wahren@i2se.com>
To: Saravana Kannan <saravanak@google.com>,
Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
kernel-team@android.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] serdev: Set fwnode for serdev devices
Date: Thu, 2 Mar 2023 18:01:33 +0100 [thread overview]
Message-ID: <2cc752fb-a25d-0789-0fad-54b99f08ced7@i2se.com> (raw)
In-Reply-To: <20230302023509.319903-1-saravanak@google.com>
Hi Saravana,
Am 02.03.23 um 03:35 schrieb Saravana Kannan:
> This allow fw_devlink to do dependency tracking for serdev devices.
>
> Reported-by: Florian Fainelli <f.fainelli@gmail.com>
> Link: https://lore.kernel.org/lkml/03b70a8a-0591-f28b-a567-9d2f736f17e5@gmail.com/
> Cc: Stefan Wahren <stefan.wahren@i2se.com>
> Signed-off-by: Saravana Kannan <saravanak@google.com>
since this fixes an issue on Raspberry Pi 4, shouldn't this be mentioned
in the commit message and providing a Fixes tag?
Thanks
Stefan
> ---
> Florian,
>
> Can you give it a shot and a tested-by please?
>
> -Saravana
>
> drivers/tty/serdev/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serdev/core.c b/drivers/tty/serdev/core.c
> index aa80de3a8194..678014253b7b 100644
> --- a/drivers/tty/serdev/core.c
> +++ b/drivers/tty/serdev/core.c
> @@ -534,7 +534,7 @@ static int of_serdev_register_devices(struct serdev_controller *ctrl)
> if (!serdev)
> continue;
>
> - serdev->dev.of_node = node;
> + device_set_node(&serdev->dev, of_fwnode_handle(node));
>
> err = serdev_device_add(serdev);
> if (err) {
next prev parent reply other threads:[~2023-03-02 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 2:35 Saravana Kannan
2023-03-02 3:53 ` Florian Fainelli
2023-03-02 17:01 ` Stefan Wahren [this message]
2023-03-02 17:20 ` Saravana Kannan
2023-03-02 17:51 ` Florian Fainelli
2023-03-02 18:07 ` Saravana Kannan
2023-03-07 4:47 ` Saravana Kannan
2023-03-07 6:51 ` Greg Kroah-Hartman
2023-03-03 11:57 ` Stefan Wahren
2023-03-03 17:22 ` Florian Fainelli
2023-03-03 21:16 ` Saravana Kannan
2023-03-05 15:00 ` Stefan Wahren
2023-03-07 3:57 ` Florian Fainelli
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=2cc752fb-a25d-0789-0fad-54b99f08ced7@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®