From: Lina Iyer <ilina@codeaurora.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org,
"open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Evan Green <evgreen@chromium.org>
Subject: Re: [PATCH v8 0/2] drivers/qcom: add Command DB support
Date: Thu, 10 May 2018 09:40:47 -0600 [thread overview]
Message-ID: <20180510154047.GJ4698@codeaurora.org> (raw)
In-Reply-To: <CAD=FV=UR03-_7bZP0_K6Gut1LMYHzopHnHbM9T3XKJw8BF1Hiw@mail.gmail.com>
On Wed, May 09 2018 at 15:30 -0600, Doug Anderson wrote:
>Lina
>
>On Wed, May 9, 2018 at 9:42 AM, Lina Iyer <ilina@codeaurora.org> wrote:
>> Hi Andy, David,
>>
>> These patches have been reviewed by our peers and have recieved no
>> further comments in the past few weeks. Would you consider merging this
>> in your trees?
>
>When I look at:
>
>https://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git/log/?h=for-next
>
>I see both of your patches (plus Stephen Boyd's patch about making
>things endian-agnostic). ...so I think we're good. :-)
>
Excellent. Thank you.
-- Lina
prev parent reply other threads:[~2018-05-10 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 17:57 [PATCH v8 0/2] drivers/qcom: add Command DB support Lina Iyer
2018-04-10 17:57 ` [PATCH v8 1/2] drivers: qcom: add command DB driver Lina Iyer
2018-04-10 17:57 ` [PATCH v8 2/2] dt-bindings: introduce Command DB for QCOM SoCs Lina Iyer
2018-05-09 16:42 ` [PATCH v8 0/2] drivers/qcom: add Command DB support Lina Iyer
2018-05-09 21:30 ` Doug Anderson
2018-05-10 15:40 ` Lina Iyer [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=20180510154047.GJ4698@codeaurora.org \
--to=ilina@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@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).