From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <balbi@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jerome Audu <jerome.audu@st.com>
Subject: Re: [PATCH] usb: dwc3: st: Rely on child's compatible instead of name
Date: Fri, 30 Sep 2022 09:14:39 +0200 [thread overview]
Message-ID: <c2b922f2-b4c3-2361-cbb0-96fe30d636f9@foss.st.com> (raw)
In-Reply-To: <YzaRm4Jtbr4F26Gt@kroah.com>
Hi Greg
On 9/30/22 08:50, Greg Kroah-Hartman wrote:
> On Fri, Sep 30, 2022 at 08:44:06AM +0200, patrice.chotard@foss.st.com wrote:
>> From: Patrice Chotard <patrice.chotard@foss.st.com>
>>
>> To ensure that child node is found, don't rely on child's node name
>> which can take different value, but on child's compatible name.
>>
>> Cc: Jerome Audu <jerome.audu@st.com>
>> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
>
> What commit id does this fix?
A fix has been already merged [1]
The goal of this patch is to hardened the child's check, but okay,
i will add a Fixes reference.
>
> Who reported the problem?
Ah, sorry, i forgot to add reported-by Felipe Balbi <felipe@balbi.sh>
Will send a v2
Thanks
Patrice
[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20220926124359.304770-1-patrice.chotard@foss.st.com
>
> thanks,
>
> greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-30 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 6:44 [PATCH] usb: dwc3: st: Rely on child's compatible instead of name patrice.chotard
2022-09-30 6:50 ` Greg Kroah-Hartman
2022-09-30 7:14 ` Patrice CHOTARD [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=c2b922f2-b4c3-2361-cbb0-96fe30d636f9@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jerome.audu@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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).