From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: Douglas Anderson <dianders@chromium.org>,
Akash Asthana <akashast@codeaurora.org>,
linux-i2c@vger.kernel.org,
Roja Rani Yarubandi <rojay@codeaurora.org>,
Stephen Boyd <swboyd@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
Mukesh Savaliya <msavaliy@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] Revert "i2c: i2c-qcom-geni: Fix DMA transfer race"
Date: Mon, 26 Oct 2020 16:15:34 -0500 [thread overview]
Message-ID: <20201026211534.GA4001@builder.lan> (raw)
In-Reply-To: <20201026151351.GB1044@ninjato>
On Mon 26 Oct 10:13 CDT 2020, Wolfram Sang wrote:
>
> > Wolfram, would you like to pick this patch or would you prefer that it
> > goes together with the other two through the soc tree?
>
> Actually, I prefer the soc tree because of the functional dependency. I
> am not aware of any pending qcom-geni patches, yet I think an immutable
> branch for me to pull in would be nice in this case. Could you provide
> one for me?
>
Sounds good, please find the series applied on top of v5.10-rc1 at:
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/20201013212531.428538-1-dianders@chromium.org
I've merged the same into the qcom tree for 5.11.
Regards,
Bjorn
next prev parent reply other threads:[~2020-10-26 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 21:25 [PATCH v2 0/3] i2c: i2c-qcom-geni: More properly fix the DMA race Douglas Anderson
2020-10-13 21:25 ` [PATCH v2 1/3] soc: qcom: geni: More properly switch to DMA mode Douglas Anderson
2020-10-13 21:25 ` [PATCH v2 2/3] Revert "i2c: i2c-qcom-geni: Fix DMA transfer race" Douglas Anderson
2020-10-26 15:05 ` Bjorn Andersson
2020-10-26 15:13 ` Wolfram Sang
2020-10-26 21:15 ` Bjorn Andersson [this message]
2020-11-03 20:35 ` Wolfram Sang
2020-10-13 21:25 ` [PATCH v2 3/3] soc: qcom: geni: Optimize/comment select fifo/dma mode Douglas Anderson
2020-10-14 9:17 ` Akash Asthana
2020-10-14 23:51 ` Stephen Boyd
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=20201026211534.GA4001@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=akashast@codeaurora.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msavaliy@codeaurora.org \
--cc=rojay@codeaurora.org \
--cc=swboyd@chromium.org \
--cc=wsa@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).