From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: stingray: Add otp device node
Date: Mon, 4 Jun 2018 14:33:36 -0700 [thread overview]
Message-ID: <efaf0373-2959-b238-e5f3-ae7e16534384@gmail.com> (raw)
In-Reply-To: <f6f3e76e-eac9-797d-fea5-eac64327ec7f@broadcom.com>
On 06/04/2018 02:30 PM, Scott Branden wrote:
> Hi Florian,
>
>
> On 18-06-04 02:24 PM, Florian Fainelli wrote:
>> On 05/23/2018 01:17 PM, Scott Branden wrote:
>>> Add otp device node for Stingray SOC.
>>>
>>> Fixes: 2fa9e9e29ea2 ("arm64: dts: Add GPIO DT nodes for Stingray SOC")
>>> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
>> Applied to devicetree-arm64/next with s/otp/OTP/ and removing the Fixes
>> line since that is not a bug fix AFAICT.
> It fixes the issue that OTP is not active as it is missing the device node?
By that token, any peripheral that is being added at some point in the
lifetime of this DTS would qualify as a bugfix when it is in fact
feature/peripheral enabling.
I could not see the relationship between the commit being provided in
the "Fixes:" tag and OTP, am I missing something?
--
Florian
next prev parent reply other threads:[~2018-06-04 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 20:17 [PATCH] arm64: dts: stingray: Add otp device node Scott Branden
2018-06-04 21:24 ` Florian Fainelli
2018-06-04 21:30 ` Scott Branden
2018-06-04 21:33 ` Florian Fainelli [this message]
2018-06-04 22:33 ` Scott Branden
2018-06-04 22:41 ` Florian Fainelli
2018-06-04 23:09 ` Scott Branden
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=efaf0373-2959-b238-e5f3-ae7e16534384@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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