From: Eduardo Valentin <edubezval@gmail.com>
To: Andy Gross <andygro@gmail.com>
Cc: Amit Kucheria <amit.kucheria@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
Kevin Hilman <khilman@baylibre.com>,
kernel-build-reports@lists.linaro.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: next/pending-fixes boot: 227 boots: 6 failed, 198 passed with 20 offline, 1 untried/unknown, 2 conflicts (v5.2-rc1-375-g3695b18d1e9cd)
Date: Tue, 28 May 2019 18:06:28 -0700 [thread overview]
Message-ID: <20190529010627.GA8566@localhost.localdomain> (raw)
In-Reply-To: <CAJ=6tTr4EaLLiavN+aRpU3JnJ5MuAtU-uer_8iLm7QMh6i4rAg@mail.gmail.com>
Hello,
On Tue, May 28, 2019 at 04:37:15PM -0500, Andy Gross wrote:
> +Eduardo
>
> On Tue, May 28, 2019 at 1:09 PM Andy Gross <andygro@gmail.com> wrote:
>
> > On Sun, May 26, 2019 at 4:51 PM Amit Kucheria <amit.kucheria@linaro.org>
> > wrote:
> >
> > <snip>
> >
> > > Sorry for breaking the boot on 8064. That was one of the platforms
> > > that I didn't convert over to regmap (needs more refactoring). I had
> > > hoped kernelci would catch any issues but looks like thermal-soc tree
> > > entered linux-next quite late and didn't catch this.
> > >
> > > Does reverting 3e6a8fb33084 ("drivers: thermal: tsens: Add new
> > > operation to check if a sensor is enabled") fix the issue? If so,
> > > reverting that commit might be the best course of action since I've
> > > started vacations and can't fix this for 8064 in a meaningful amount
> > > of time (until 3rd week of June). cc'ing Bjorn in case this needs more
> > > investigation, but I think that patch is fairly self contained and
> > > reverting it shouldn't have any knock-on effects.
> >
> > I am ok with this. I'll check with Bjorn before adding this to a
> > fixes for -rc2.
> >
>
> Eduardo, we have a situation with the Qcom tsens driver and
> commit 3e6a8fb33084. Do you mind if I send in a revert for this through
> my tree or can you do this for us for -rc2?
I can revert this patch. I can confirm that it is selfcontained and
reverting seams to work. I am sending the revert to -rc3, as rc2 is
already out.
>
> Thanks,
> Andy
next prev parent reply other threads:[~2019-05-29 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ce71d79.1c69fb81.dd0de.33cf@mx.google.com>
[not found] ` <7hv9y01z85.fsf@baylibre.com>
2019-05-24 1:29 ` next/pending-fixes boot: 227 boots: 6 failed, 198 passed with 20 offline, 1 untried/unknown, 2 conflicts (v5.2-rc1-375-g3695b18d1e9cd) Stephen Boyd
2019-05-26 21:51 ` Amit Kucheria
2019-05-28 18:09 ` Andy Gross
[not found] ` <CAJ=6tTr4EaLLiavN+aRpU3JnJ5MuAtU-uer_8iLm7QMh6i4rAg@mail.gmail.com>
2019-05-29 1:06 ` Eduardo Valentin [this message]
2019-05-29 1:19 ` Andy Gross
2019-05-29 2:34 ` [PATCH 1/1] Revert "drivers: thermal: tsens: Add new operation to check if a sensor is enabled" Eduardo Valentin
2019-05-28 20:17 ` next/pending-fixes boot: 227 boots: 6 failed, 198 passed with 20 offline, 1 untried/unknown, 2 conflicts (v5.2-rc1-375-g3695b18d1e9cd) Kevin Hilman
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=20190529010627.GA8566@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=amit.kucheria@linaro.org \
--cc=andygro@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-msm@vger.kernel.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).