linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adrian Schmutzler" <mail@adrianschmutzler.de>
To: "'Bjorn Andersson'" <bjorn.andersson@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: RE: [PATCH 2/2] arm64: dts: replace status value "ok" by "okay"
Date: Sat, 26 Sep 2020 19:03:35 +0200	[thread overview]
Message-ID: <011401d69426$f8e23250$eaa696f0$@adrianschmutzler.de> (raw)
In-Reply-To: <20200901163125.GZ3715@yoga>

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

Hi,

> -----Original Message-----
> From: Bjorn Andersson [mailto:bjorn.andersson@linaro.org]
> Sent: Dienstag, 1. September 2020 18:31
> To: Adrian Schmutzler <mail@adrianschmutzler.de>
> Cc: linux-arm-msm@vger.kernel.org; devicetree@vger.kernel.org
> Subject: Re: [PATCH 2/2] arm64: dts: replace status value "ok" by "okay"
> 
> On Tue 01 Sep 11:00 CDT 2020, Adrian Schmutzler wrote:
> 
> > > -----Original Message-----
> > > From: Bjorn Andersson [mailto:bjorn.andersson@linaro.org]
> > > Sent: Sonntag, 30. August 2020 19:32
> > > To: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> > > Cc: linux-arm-msm@vger.kernel.org; devicetree@vger.kernel.org
> > > Subject: Re: [PATCH 2/2] arm64: dts: replace status value "ok" by "okay"
> > >
> > > On Mon 17 Aug 22:32 UTC 2020, Adrian Schmutzler wrote:
> > >
> > > > While the DT parser recognizes "ok" as a valid value for the "status"
> > > > property, it is actually mentioned nowhere. Use the proper value
> > > > "okay" instead, as done in the majority of files already.
> > > >
> > > > Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> > >
> > > The content of this looks good Adrian.
> > >
> > > But you're lacking most maintainers among the recipients of these
> > > patches and I would expect if applied in the current form we will
> > > have merge issues as the patches travels towards Linus' tree.
> > >
> > > So please split it per vendor and ensure that the various
> > > maintainers are copied (use ./scripts/get_maintainer.pl)
> >
> > Thanks for the instructions, I was used to a different submission behavior.
> >
> > I split stuff up (all of ARM64 and most of ARM changes) and submitted
> > them separately via the recommended way.
> >
> 
> Thank you,
> Bjorn

Thanks for merging the arm64/qcom patch.

I'd be very happy if you could also pick the similar patch for ARM, as the ipq8064 platform is actually the reason why I made this effort in the first place:

https://patchwork.kernel.org/patch/11745289/

Best

Adrian

[-- Attachment #2: openpgp-digital-signature.asc --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

      reply	other threads:[~2020-09-26 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 22:32 [PATCH 1/2] arm: dts: replace status value "ok" by "okay" Adrian Schmutzler
2020-08-17 22:32 ` [PATCH 2/2] arm64: " Adrian Schmutzler
2020-08-30 17:32   ` Bjorn Andersson
2020-09-01 16:00     ` Adrian Schmutzler
2020-09-01 16:31       ` Bjorn Andersson
2020-09-26 17:03         ` Adrian Schmutzler [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='011401d69426$f8e23250$eaa696f0$@adrianschmutzler.de' \
    --to=mail@adrianschmutzler.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.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).