From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
linux-kernel@vger.kernel.org, bhupesh.linux@gmail.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH v5 1/5] usb: misc: eud: Fix eud sysfs path (use 'qcom_eud')
Date: Wed, 17 May 2023 11:08:38 +0530 [thread overview]
Message-ID: <20230517053838.GF4868@thinkpad> (raw)
In-Reply-To: <20230516213308.2432018-2-bhupesh.sharma@linaro.org>
On Wed, May 17, 2023 at 03:03:04AM +0530, Bhupesh Sharma wrote:
> The eud sysfs enablement path is currently mentioned in the
> Documentation as:
> /sys/bus/platform/drivers/eud/.../enable
>
> Instead it should be:
> /sys/bus/platform/drivers/qcom_eud/.../enable
>
> Fix the same.
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
I believe the path has changed during one of the EUD patch iterations. In that
case, the documentation is wrong from day one. So this patch should have the
relevant Fixes tag.
With that,
Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
> ---
> Documentation/ABI/testing/sysfs-driver-eud | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-driver-eud b/Documentation/ABI/testing/sysfs-driver-eud
> index 83f3872182a4..2bab0db2d2f0 100644
> --- a/Documentation/ABI/testing/sysfs-driver-eud
> +++ b/Documentation/ABI/testing/sysfs-driver-eud
> @@ -1,4 +1,4 @@
> -What: /sys/bus/platform/drivers/eud/.../enable
> +What: /sys/bus/platform/drivers/qcom_eud/.../enable
> Date: February 2022
> Contact: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
> Description:
> --
> 2.38.1
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-05-17 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 21:33 [PATCH v5 0/5] Add Qualcomm SM6115 / SM4250 EUD dt-bindings & driver support Bhupesh Sharma
2023-05-16 21:33 ` [PATCH v5 1/5] usb: misc: eud: Fix eud sysfs path (use 'qcom_eud') Bhupesh Sharma
2023-05-17 5:38 ` Manivannan Sadhasivam [this message]
2023-05-17 6:28 ` Bhupesh Sharma
2023-05-16 21:33 ` [PATCH v5 2/5] dt-bindings: soc: qcom: eud: Add SM6115 / SM4250 support Bhupesh Sharma
2023-05-17 14:55 ` Krzysztof Kozlowski
2023-05-16 21:33 ` [PATCH v5 3/5] usb: misc: eud: Add driver support for SM6115 / SM4250 Bhupesh Sharma
2023-05-17 4:50 ` Greg KH
2023-05-17 6:33 ` Bhupesh Sharma
2023-05-16 21:33 ` [PATCH v5 4/5] arm64: dts: qcom: sm6115: Add EUD dt node and dwc3 connector Bhupesh Sharma
2023-05-16 21:33 ` [PATCH v5 5/5] arm64: dts: qcom: qrb4210-rb2: Enable EUD debug peripheral Bhupesh Sharma
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=20230517053838.GF4868@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@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).