From: Nishanth Menon <nm@ti.com>
To: Judith Mendez <jm@ti.com>
Cc: Matt Ranostay <mranostay@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <miquel.raynal@bootlin.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: rename clock-names adc_tsc_fck to fck
Date: Wed, 2 Nov 2022 16:32:31 -0500 [thread overview]
Message-ID: <20221102213231.zljnsdpmfcht7xvw@mascot> (raw)
In-Reply-To: <615d6805-4b0c-c3ad-f4d7-dc0536e6cabe@ti.com>
On 15:14-20221102, Judith Mendez wrote:
> Hello,
>
> On 10/24/22 10:16, Matt Ranostay wrote:
> > Avoid the following warnings from dt-schema by just renaming the
> > clock-names string from adc_tsc_fck to fck so it matches the values in
> > ti,am3359-tscadc.yaml
> >
> > tscadc@40200000: clock-names:0: 'fck' was expected
> >
>
> Tested on AM64x GP EVM.
>
> Verified-by: Judith Mendez <jm@ti.com>
Documentation/process/submitting-patches.rst Could you use the standard
conventions defined there? I think you mean Tested-by? if so, please use
that tag.
Quote from documentation:
"A Tested-by: tag indicates that the patch has been successfully tested (in
some environment) by the person named. This tag informs maintainers that
some testing has been performed, provides a means to locate testers for
future patches, and ensures credit for the testers.
"
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-02 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 15:16 [PATCH] arm64: dts: ti: rename clock-names adc_tsc_fck to fck Matt Ranostay
2022-10-28 5:37 ` Gole, Dhruva
2022-11-02 20:14 ` Judith Mendez
2022-11-02 21:32 ` Nishanth Menon [this message]
2022-11-03 7:23 ` Nishanth Menon
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=20221102213231.zljnsdpmfcht7xvw@mascot \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mranostay@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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