From: Linus Walleij <linus.walleij@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] pinctrl: qcom: Add sdm845 pinctrl driver
Date: Tue, 6 Feb 2018 14:37:49 +0100 [thread overview]
Message-ID: <CACRpkdYvLnWxQcF3188PnrCmsmSqPQPicT7HvPknOe4Akt8uKg@mail.gmail.com> (raw)
In-Reply-To: <20180111060004.9333-2-bjorn.andersson@linaro.org>
On Thu, Jan 11, 2018 at 7:00 AM, Bjorn Andersson
<bjorn.andersson@linaro.org> wrote:
> From: Kyle Yan <kyan@codeaurora.org>
>
> This adds the pinctrl definitions for the TLMM of SDM845.
>
> Signed-off-by: Kyle Yan <kyan@codeaurora.org>
> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Patch applied for v4.17.
> Changes since v1:
> - Corrected the authorship of the patch
> - Updated pin list to v2 hardware
Does that mean the v1 hardware is some prototype, only existing inside
Qualcomm & associates, all of which needs to be trashed now?
I hope it doesn't mean "oh yeah we shipped a few
million phones with that but they need to have a different kernel
and will never work with upstream".
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-02-06 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 6:00 [PATCH v2 1/2] dt-bindings: pinctrl: Add Qualcomm SDM845 TLMM binding Bjorn Andersson
2018-01-11 6:00 ` [PATCH v2 2/2] pinctrl: qcom: Add sdm845 pinctrl driver Bjorn Andersson
2018-02-06 13:37 ` Linus Walleij [this message]
2018-01-19 21:17 ` [PATCH v2 1/2] dt-bindings: pinctrl: Add Qualcomm SDM845 TLMM binding Rob Herring
2018-02-06 13:34 ` 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=CACRpkdYvLnWxQcF3188PnrCmsmSqPQPicT7HvPknOe4Akt8uKg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).