From: Manu Gautam <mgautam@codeaurora.org>
To: Douglas Anderson <dianders@chromium.org>,
Felipe Balbi <balbi@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Sandeep Maheswaram <sanm@codeaurora.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] usb: dwc3: qcom: Remove useless compatible strings from the match table
Date: Fri, 13 Dec 2019 12:37:01 +0530 [thread overview]
Message-ID: <3fc8f36f-9ca2-7b56-9f1f-94507481b715@codeaurora.org> (raw)
In-Reply-To: <20191212132122.1.I85a23bdcff04dbce48cc46ddb8f1ffe7a51015eb@changeid>
Thanks. Patch looks good to me.
On 12/13/2019 2:51 AM, Douglas Anderson wrote:
> The of match table in dwc3-qcom.c had an entry per Qualcomm SoC known
> to have dwc3. That's not needed. Here's why:
>
> 1. The bindings specify that the compatible string in the device tree
> should contain the SoC-specific compatible string followed by the
> string "qcom,dwc3".
>
> 2. All known Qualcomm SoC dts files (confirmed via git grep in
> mainline Linux) using dwc3 follow the rules and do, in fact,
> contain the SoC-specific compatible string followed by the string
> "qcom,dwc3".
>
> 3. The source code does nothing special with the per-SoC strings--they
> are only used to match the node.
>
> Let's remove the extra strings from the table. Doing so will avoid
> the need to land future useless patches [1] that do nothing more than
> add yet more strings to the table.
Reviewed-by: Manu Gautam <mgautam@codeaurora.org>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2019-12-13 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 21:21 [PATCH] usb: dwc3: qcom: Remove useless compatible strings from the match table Douglas Anderson
2019-12-12 23:23 ` Bjorn Andersson
2019-12-13 7:07 ` Manu Gautam [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=3fc8f36f-9ca2-7b56-9f1f-94507481b715@codeaurora.org \
--to=mgautam@codeaurora.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sanm@codeaurora.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).