From: Rob Herring <robh@kernel.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: add Huawei
Date: Tue, 11 Jan 2022 20:14:14 -0600 [thread overview]
Message-ID: <Yd45dgW8Fgsmuzrm@robh.at.kernel.org> (raw)
In-Reply-To: <20220110121307.GA1894@standask-GA-A55M-S2HP>
On Mon, Jan 10, 2022 at 01:13:07PM +0100, Stanislav Jakubek wrote:
> On Mon, Jan 10, 2022 at 09:55:43AM +0000, Jonathan Cameron wrote:
> > On Sun, 9 Jan 2022 14:23:11 +0100
> > Stanislav Jakubek <stano.jakubek@gmail.com> wrote:
> >
> > > Add vendor prefix for Huawei (https://www.huawei.com/en/)
> >
> > Patch description should say why... Is there an existing binding
> > using a huawei vendor prefix?
>
> Not sure about bindings, but there are device trees using the huawei
> vendor prefix. I'm aware of at least these two:
> /arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dts
> /arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
>
> Similar situation with the other vendor prefix patches I've sent yesterday.
>
> Should I send a v2 with an updated patch description for this and
> the other patches?
Yes.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: add Huawei
Date: Tue, 11 Jan 2022 20:14:14 -0600 [thread overview]
Message-ID: <Yd45dgW8Fgsmuzrm@robh.at.kernel.org> (raw)
In-Reply-To: <20220110121307.GA1894@standask-GA-A55M-S2HP>
On Mon, Jan 10, 2022 at 01:13:07PM +0100, Stanislav Jakubek wrote:
> On Mon, Jan 10, 2022 at 09:55:43AM +0000, Jonathan Cameron wrote:
> > On Sun, 9 Jan 2022 14:23:11 +0100
> > Stanislav Jakubek <stano.jakubek@gmail.com> wrote:
> >
> > > Add vendor prefix for Huawei (https://www.huawei.com/en/)
> >
> > Patch description should say why... Is there an existing binding
> > using a huawei vendor prefix?
>
> Not sure about bindings, but there are device trees using the huawei
> vendor prefix. I'm aware of at least these two:
> /arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dts
> /arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
>
> Similar situation with the other vendor prefix patches I've sent yesterday.
>
> Should I send a v2 with an updated patch description for this and
> the other patches?
Yes.
Rob
_______________________________________________
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-01-12 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 13:23 [PATCH] dt-bindings: vendor-prefixes: add Huawei Stanislav Jakubek
2022-01-09 13:23 ` Stanislav Jakubek
2022-01-10 9:55 ` Jonathan Cameron
2022-01-10 9:55 ` Jonathan Cameron
2022-01-10 12:13 ` Stanislav Jakubek
2022-01-10 12:13 ` Stanislav Jakubek
2022-01-12 2:14 ` Rob Herring [this message]
2022-01-12 2:14 ` Rob Herring
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=Yd45dgW8Fgsmuzrm@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stano.jakubek@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.