From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Jimmy Chen <jinghung.chen3@hotmail.com>,
Andy Gross <agross@kernel.org>,
alan-huang@quanta.corp-partner.google.com,
Bjorn Andersson <bjorn.andersson@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/2] [V1,1/2] arm64: dts: qcom: Add LTE SKUs for sc7280-villager family
Date: Thu, 7 Jul 2022 08:22:00 +0200 [thread overview]
Message-ID: <d3d4d90b-85b5-5ad9-78e6-5a074c21af4f@linaro.org> (raw)
In-Reply-To: <CAD=FV=WtKRFQr5jSQvsr08x9dgHrvenUWWtX_SKuCLuSvSH7WQ@mail.gmail.com>
On 07/07/2022 01:40, Doug Anderson wrote:
> Relevant links:
>
> * You saying you liked the enum [1].
> * Me saying I liked them separate and that switching from a
> "description" to a comment was opposite of what Stephen had previous
> voted for [2], but could change if there was overwhelming need to make
> them an enum.
> * Rob saying he prefers an enum but lets sub-arch maintainers decide [3].
> * Bjorn (the sub-arch maintainer) landing the patch without the enum [4].
Ah, so the argument to my comment about using enum was that Bjorn
apparently prefers such way. OK.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-07-07 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 7:09 [PATCH 1/2] [V1,1/2] arm64: dts: qcom: Add LTE SKUs for sc7280-villager family Jimmy Chen
2022-07-04 9:02 ` Krzysztof Kozlowski
2022-07-06 9:36 ` Jimmy Chen
2022-07-06 10:04 ` Krzysztof Kozlowski
2022-07-06 23:40 ` Doug Anderson
2022-07-07 6:22 ` Krzysztof Kozlowski [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=d3d4d90b-85b5-5ad9-78e6-5a074c21af4f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=alan-huang@quanta.corp-partner.google.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=jinghung.chen3@hotmail.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.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 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.