From: Wolfram Sang <wsa@the-dreams.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
agross@kernel.org, alokc@codeaurora.org,
bjorn.andersson@linaro.org, mark.rutland@arm.com,
robh+dt@kernel.org, vkoul@kernel.org, linux-i2c@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RESEND v3 1/1] i2c: qcom-geni: Disable DMA processing on the Lenovo Yoga C630
Date: Fri, 6 Sep 2019 08:50:18 +0200 [thread overview]
Message-ID: <20190906065018.GA1019@kunai> (raw)
In-Reply-To: <20190906061448.GJ26880@dell>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
> > This compatible isn't in the 5.3 rc series nor is it in linux-next yet.
> > Is this "hot-fix" for the next merge window? Or is this compatible
> > string being generated by firmware somewhere and thus isn't part of the
> > kernel?
>
> It's on the list and will be in all of the distro v5.3 release kernels.
>
> https://lkml.org/lkml/2019/9/5/695
And why don't the distro kernels simply pick up this patch, too?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-06 6:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 19:24 [RESEND v3 1/1] i2c: qcom-geni: Disable DMA processing on the Lenovo Yoga C630 Lee Jones
2019-09-05 20:22 ` Wolfram Sang
2019-09-06 5:33 ` Stephen Boyd
2019-09-06 5:33 ` Stephen Boyd
2019-09-06 6:14 ` Lee Jones
2019-09-06 6:50 ` Wolfram Sang [this message]
2019-09-06 7:56 ` Lee Jones
2019-09-06 10:23 ` Wolfram Sang
2019-09-06 10:54 ` Lee Jones
2019-09-06 18:31 ` Wolfram Sang
2019-09-07 17:56 ` Rob Clark
2019-09-13 14:28 ` Wolfram Sang
2019-09-13 16:13 ` Bjorn Andersson
2019-09-13 16:17 ` Wolfram Sang
2019-09-14 8:57 ` Lee Jones
2019-09-25 15:38 ` Lee Jones
2019-09-27 21:17 ` Lee Jones
2019-09-14 19:13 ` Arnd Bergmann
2019-09-28 17:48 ` Wolfram Sang
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=20190906065018.GA1019@kunai \
--to=wsa@the-dreams.de \
--cc=agross@kernel.org \
--cc=alokc@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.