From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] ARM: dts: integratorap: Update spi node properties
Date: Thu, 25 Aug 2022 08:31:28 +0530 [thread overview]
Message-ID: <20220825030128.GA34813@9a2d8922b8f1> (raw)
In-Reply-To: <CACRpkdY2_SC0o-h19+kViBpgMSoBBm_gWv8DqYdzo_h=dOj-6w@mail.gmail.com>
On Thu, Aug 25, 2022 at 12:15:17AM +0200, Linus Walleij wrote:
> On Mon, Aug 15, 2022 at 7:30 PM Kuldeep Singh
> <singh.kuldeep87k@gmail.com> wrote:
> >
> > > > This and patches 2, 3/4 applied to the versatile DTS branch.
> > >
> > > What happened to this?
> >
> > Thanks Rob for pointing this out, I lost track for these changes.
> > I just noticed Linus applied ste-dbx change only and skipped others(integrator,
> > realview, versatile).
> >
> > These patches fix clock-name as per pl022 binding which causes no harm.
> > Linus, Any reason to skip others?
>
> I just forgot to send them. I'll fix.
Ok np. Thanks!
--
Kuldeep
next prev parent reply other threads:[~2022-08-25 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 11:38 [PATCH v3 0/4] DT fixes for pl022 for arm platforms Kuldeep Singh
2022-03-12 11:38 ` [PATCH v3 1/4] ARM: dts: integratorap: Update spi node properties Kuldeep Singh
2022-03-24 22:07 ` Linus Walleij
2022-08-10 19:46 ` Rob Herring
2022-08-15 17:30 ` Kuldeep Singh
2022-08-24 22:15 ` Linus Walleij
2022-08-25 3:01 ` Kuldeep Singh [this message]
2022-08-24 22:14 ` Linus Walleij
2022-03-12 11:38 ` [PATCH v3 2/4] ARM: dts: realview: Update spi clock-names property Kuldeep Singh
2022-03-12 11:38 ` [PATCH v3 3/4] ARM: dts: versatile: " Kuldeep Singh
2022-03-12 11:38 ` [PATCH v3 4/4] ARM: dts: ste-dbx: " Kuldeep Singh
2022-03-14 22:28 ` Linus Walleij
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=20220825030128.GA34813@9a2d8922b8f1 \
--to=singh.kuldeep87k@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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).