stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Sasha Levin <Alexander.Levin@microsoft.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [GIT PULL] commits for Linux 4.4
Date: Fri, 27 Apr 2018 11:04:46 -0700	[thread overview]
Message-ID: <20180427180446.GA18615@flashbox> (raw)
In-Reply-To: <6cd50d5c-89ec-b484-d684-6ee316575d87@codeaurora.org>

On Fri, Apr 27, 2018 at 03:40:50AM -0500, Timur Tabi wrote:
> On 4/27/18 2:35 AM, Nathan Chancellor wrote:
> > > That's not good.  Have you reported this to the gpio developers and
> > > authors of that patch?
> > > 
> > I have not although I've gone ahead and CC'd them on this email.
> > 
> > > > I'm happy to carry the revert in my tree given it is probably a correct
> > > > change in mainline but I figured I would let you guys know so you can
> > > > make that decision.
> > > Ah, do you think this is a userspace issue with your device and not a
> > > kernel problem?  That implies that this patch isn't ok and should be
> > > reverted upstream.
> > > 
> > I don't think this is a userspace regression. My guess is certain
> > out of tree drivers expect a static base value, based on the wording
> > of the commit message. Unfortunately, his is all a little bit over
> > my head at the moment. I will try to study up on it tomorrow. I just
> > wanted to report the regression as soon as I uncovered it (I'd be
> > lying if I said I liked reporting bugs heh).
> 
> Apparently, user-space should no longer be depending on any base value.
> Instead, gpiolib should be used.  I'm guessing that the Pixel 2 XL does not
> use gpiolib, since gpiolib didn't exist until Linux 4.8.
> 
> So I think that this patch should be reverted in 4.4.
> 
> When the patch was submitted, I proposed an alternative that would preserve
> existing platforms but still support gpiolib and newer systems with multiple
> TLMMs:
> 
> 	https://lkml.org/lkml/2018/2/7/360
> 
> I thought it was a good compromise, but it was rejected.
> 
> -- 
> Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
> Technologies, Inc.  Qualcomm Technologies, Inc. is a member of the
> Code Aurora Forum, a Linux Foundation Collaborative Project.

Thank you very much for the quick response and explanation. Makes
perfect. Glad we caught it before it even made it into an RC release.

Cheers!
Nathan

  reply	other threads:[~2018-04-27 18:04 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27  2:01 [GIT PULL] commits for Linux 4.4 Sasha Levin
2018-04-27  4:50 ` Nathan Chancellor
2018-04-27  7:05   ` Greg KH
2018-04-27  7:35     ` Nathan Chancellor
2018-04-27  8:40       ` Timur Tabi
2018-04-27 18:04         ` Nathan Chancellor [this message]
2018-04-30 17:21       ` Bjorn Andersson
2018-04-30 17:34         ` Nathan Chancellor
2018-04-30 18:01           ` Bjorn Andersson
2018-04-27  8:15     ` Harsh Shandilya
2018-05-02 20:09 ` Greg KH
2018-05-03  6:23 ` Amit Pundir
2018-05-03 12:00   ` Greg KH
2018-05-03  6:49 ` Amit Pundir
2018-05-03 15:51   ` Greg KH
2018-05-03 15:51     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2018-11-12  3:26 Sasha Levin
2018-11-05 19:09 Sasha Levin
2018-10-22  9:14 Sasha Levin
2018-10-16 16:40 Sasha Levin
2018-10-12 14:36 Sasha Levin
2018-10-08 15:02 Sasha Levin
2018-10-02  0:58 Sasha Levin
2018-09-28  0:26 Sasha Levin
2018-09-24  1:01 Sasha Levin
2018-09-17 23:46 Sasha Levin
2018-09-14 18:41 Sasha Levin
2018-09-10 14:28 Sasha Levin
2018-08-25 15:10 Sasha Levin
2018-08-28 14:12 ` Greg KH
2018-08-10  0:23 Sasha Levin
2018-08-22  8:37 ` Greg KH
2018-07-28  1:46 Sasha Levin
2018-07-28 10:28 ` Greg KH
2018-06-21  2:37 Sasha Levin
2018-07-05 18:18 ` Greg KH
2018-07-05 19:09   ` Sasha Levin
2018-06-07  1:07 Sasha Levin
2018-06-05  4:00 Sasha Levin
2018-05-19 16:59 Sasha Levin
2018-05-28  8:04 ` Greg KH
2018-04-15 21:38 Sasha Levin
2018-04-24 17:03 ` Greg KH
2018-04-05  6:24 Sasha Levin
2018-04-10  8:50 ` Greg KH
2018-03-19 15:38 Sasha Levin
2018-03-22 14:11 ` Greg KH
2018-03-15 22:40 Sasha Levin
2018-03-19  9:09 ` Greg KH
2018-02-25  0:59 Sasha Levin
2018-02-28 15:20 ` Greg KH
2018-02-04 16:03 Sasha Levin
2018-02-23 10:59 ` Greg KH
2018-01-28 22:32 Sasha Levin
2017-12-20 15:37 alexander.levin
2017-12-21  9:51 ` Greg KH
2017-12-14 16:13 alexander.levin
2017-12-18 14:01 ` Greg KH
2017-12-12  0:59 alexander.levin
2017-12-12 12:45 ` Greg KH
2017-12-02 15:45 alexander.levin
2017-12-06 16:31 ` Greg KH
2017-11-30 22:02 alexander.levin
2017-11-30 22:01 alexander.levin
2017-11-24 17:14 alexander.levin
2017-11-28  9:57 ` Greg KH
2017-11-19  0:51 alexander.levin
2017-11-19 11:05 ` Greg KH
2017-11-08 20:45 Levin, Alexander (Sasha Levin)
2017-11-09 17:26 ` Greg KH
2017-10-25  1:39 Levin, Alexander (Sasha Levin)
2017-11-06  9:25 ` Greg KH

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=20180427180446.GA18615@flashbox \
    --to=natechancellor@gmail.com \
    --cc=Alexander.Levin@microsoft.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=stable@vger.kernel.org \
    --cc=timur@codeaurora.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).