From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: ns2: Fix spi-cpol and spi-cpha property
Date: Wed, 2 Mar 2022 18:37:34 +0530 [thread overview]
Message-ID: <20220302130734.GA2026@9a2d8922b8f1> (raw)
In-Reply-To: <bdb6a903-6efc-e7ff-3a88-70ad9fe3fc09@gmail.com>
On Mon, Feb 28, 2022 at 01:31:50PM -0800, Florian Fainelli wrote:
>
>
> On 2/28/2022 3:09 AM, Kuldeep Singh wrote:
> > Broadcom ns2 platform has spi-cpol and spi-cpho properties set
> > incorrectly. As per spi-slave-peripheral-prop.yaml, these properties are
> > of flag or boolean type and not integer type. Fix the values.
> >
> > CC: Ray Jui <rjui@broadcom.com>
> > CC: Scott Branden <sbranden@broadcom.com>
> > CC: Florian Fainelli <f.fainelli@gmail.com>
> > Fixes: d69dbd9f41a7c (arm64: dts: Add ARM PL022 SPI DT nodes for NS2)
> > Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
> > ---
> > Hi,
> >
> > This patch is on top of git://github.com/broadcom/cygnus-linux.git,
> > master branch which is not updated since 4.14 kernel.
> > Hope the reference is correct. Thanks!
>
> The reference is not correct, but it applied cleanly anyway. The correct
> reference would have been the github.com/Broadcom/stblinux
> refs/heads/devicetree-arm64/next
Thanks Florian for mentioning.
I took a quick look at MAINTAINERS file before sending patch and found
cygnus-linux repo as base reference. It seems the correct reference is
not updated in MAINTAINERS file.
>
> Applied, thanks!
Thanks!
--
Best Regards
Kuldeep
prev parent reply other threads:[~2022-03-02 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 11:09 [PATCH] arm64: dts: ns2: Fix spi-cpol and spi-cpha property Kuldeep Singh
2022-02-28 21:31 ` Florian Fainelli
2022-03-02 13:07 ` Kuldeep Singh [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=20220302130734.GA2026@9a2d8922b8f1 \
--to=singh.kuldeep87k@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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).