From: Florian Fainelli <f.fainelli@gmail.com>
To: Saravana Kannan <saravanak@google.com>,
Stefan Wahren <stefan.wahren@i2se.com>
Cc: Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
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 09:51:04 -0800 [thread overview]
Message-ID: <faad8810-7aa4-e122-f497-73553feb8bcd@gmail.com> (raw)
In-Reply-To: <CAGETcx_nCdm2WYLC7h1s8i9tnHc_LcHk2oZUQ0sUDr-PBsUWDg@mail.gmail.com>
On 3/2/2023 9:20 AM, Saravana Kannan wrote:
> On Thu, Mar 2, 2023 at 9:01 AM Stefan Wahren <stefan.wahren@i2se.com> wrote:
>>
>> 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?
>
> So RPi 4 was never creating a device links between serdev devices and
> their consumers. The error message was just a new one I added and we
> are noticing and catching the fact that serdev wasn't setting fwnode
> for a device.
>
> I'm also not sure if I can say this commit "Fixes" an issue in serdev
> core because when serdev core was written, fw_devlink wasn't a thing.
> Once I add Fixes, people will start pulling this into stable
> branches/other trees where I don't think this should be pulled into
> older stable branches.
That is kind of the point of Fixes: tag, is not it? It is appropriate to
list a commit that is not specific to serdev, but maybe a particular
point into the fw_devlink history. Given this did not appear to have a
functional impact, we could go without one.
--
Florian
next prev parent reply other threads:[~2023-03-02 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 2:35 [PATCH v1] serdev: Set fwnode for serdev devices Saravana Kannan
2023-03-02 3:53 ` Florian Fainelli
2023-03-02 17:01 ` Stefan Wahren
2023-03-02 17:20 ` Saravana Kannan
2023-03-02 17:51 ` Florian Fainelli [this message]
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=faad8810-7aa4-e122-f497-73553feb8bcd@gmail.com \
--to=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 \
--cc=stefan.wahren@i2se.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