From: Mark Brown <broonie@kernel.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Alexandru M Stan <amstan@chromium.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Akash Asthana <akashast@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH] spi: spi-geni-qcom: Use the new method of gpio CS control
Date: Fri, 4 Dec 2020 17:00:58 +0000 [thread overview]
Message-ID: <20201204170058.GA4558@sirena.org.uk> (raw)
In-Reply-To: <8d864844-11d8-0eae-d85c-29136f035c1b@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Fri, Dec 04, 2020 at 10:13:52AM +0100, Enric Balletbo i Serra wrote:
> I am fine either way. I'm fine with pick all the patches and go through the
> chrome/platform tree if Mark is agree (I think this patch has no other
> dependencies and the patch applies cleanly to my tree) or all can go through the
> Mark's tree. If I need to an IB I can also do it without problems.
>
> I'll leave Mark to decide who has much experience solving this kind of problems.
I'm happy to take both patches, there are some others in this area in
the SPI tree so it might minimise bisection problems if I take them but
not sure if there's any actual overlap there. If someone could resend
them as a series?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-12-04 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 21:49 [PATCH] spi: spi-geni-qcom: Use the new method of gpio CS control Stephen Boyd
2020-12-02 22:18 ` Alexandru M Stan
2020-12-02 23:28 ` Stephen Boyd
2020-12-03 0:47 ` Stephen Boyd
2020-12-03 20:06 ` Doug Anderson
2020-12-04 0:10 ` Stephen Boyd
2020-12-04 9:13 ` Enric Balletbo i Serra
2020-12-04 17:00 ` Mark Brown [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=20201204170058.GA4558@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akashast@codeaurora.org \
--cc=amstan@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=bleung@chromium.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=swboyd@chromium.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).