From: Timur Tabi <timur@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002
Date: Tue, 3 Apr 2018 07:03:13 -0500 [thread overview]
Message-ID: <0fda91f1-d75b-cf2a-ed92-c17f3aba953f@codeaurora.org> (raw)
In-Reply-To: <20180403040739.GB453@tuxbook-pro>
On 4/2/18 11:07 PM, Bjorn Andersson wrote:
> I presume you're okay with not being able to run mainline on your old
> firmware?
Yes, that firmware is very old now, and it doesn't even support our
current production silicon.
>
> Acked-by: Bjorn Andersson<bjorn.andersson@linaro.org>
Thank you.
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-04-03 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 23:44 [PATCH 1/2] pinctrl: qcom: remove static globals to allow multiple TLMMs Timur Tabi
2018-03-23 23:45 ` [PATCH 2/2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
2018-04-03 4:07 ` Bjorn Andersson
2018-04-03 12:03 ` Timur Tabi [this message]
2018-04-07 12:33 ` Stephen Boyd
2018-03-27 13:33 ` [PATCH 1/2] pinctrl: qcom: remove static globals to allow multiple TLMMs Linus Walleij
2018-04-02 20:52 ` Timur Tabi
2018-04-03 4:04 ` Bjorn Andersson
2018-04-07 12:30 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2017-07-13 21:52 [PATCH 0/2] pinctrl: qcom: add support for sparse GPIOs Timur Tabi
2017-07-13 21:52 ` [PATCH 2/2] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002 Timur Tabi
2017-07-14 17:21 ` Bjorn Andersson
2017-07-14 18:30 ` Timur Tabi
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=0fda91f1-d75b-cf2a-ed92-c17f3aba953f@codeaurora.org \
--to=timur@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sboyd@codeaurora.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).