From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Roger Lu (陸瑞傑)" <Roger.Lu@mediatek.com>,
"matthias.bgg@kernel.org" <matthias.bgg@kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"nfraprado@collabora.com" <nfraprado@collabora.com>
Subject: Re: [PATCH] soc: mediatek: mtk-svs: delete node name check
Date: Tue, 14 Feb 2023 14:54:58 +0100 [thread overview]
Message-ID: <1258b5b7-e8c8-cfb1-5bfb-c966dd4cfcf8@gmail.com> (raw)
In-Reply-To: <65af4673ef79d8dd3404f4cfb773859410c85cc5.camel@mediatek.com>
On 11/02/2023 12:37, Roger Lu (陸瑞傑) wrote:
> On Fri, 2023-02-10 at 13:01 +0100, AngeloGioacchino Del Regno wrote:
>> Il 09/02/23 17:24, matthias.bgg@kernel.org ha scritto:
>>> From: Matthias Brugger <matthias.bgg@gmail.com>
>>>
>>> The function svs_add_device_link is called only internally from the SoC
>>> specific probe functions. We don't need to check if the node_name is
>>> null because that would mean that we have a buggy SoC probe function in
>>> the first place.
>>>
>>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>>
>> Reviewed-by: AngeloGioacchino Del Regno <
>> angelogioacchino.delregno@collabora.com>
>
> Reviewed-by: Roger Lu <roger.lu@mediatek.com>
Applied, thanks for the reviews.
Matthias
_______________________________________________
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:[~2023-02-14 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 16:24 [PATCH] soc: mediatek: mtk-svs: delete node name check matthias.bgg
2023-02-10 12:01 ` AngeloGioacchino Del Regno
2023-02-11 11:37 ` Roger Lu (陸瑞傑)
2023-02-14 13:54 ` Matthias Brugger [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=1258b5b7-e8c8-cfb1-5bfb-c966dd4cfcf8@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Roger.Lu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@kernel.org \
--cc=nfraprado@collabora.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;
as well as URLs for NNTP newsgroup(s).