On Mon, May 28, 2018 at 02:17:21PM +0530, Harsh Shandilya wrote: > On 28 May 2018 1:48:31 PM IST, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > >On Mon, May 28, 2018 at 10:04:52AM +0200, Greg KH wrote: > >> On Sat, May 19, 2018 at 04:59:29PM +0000, Sasha Levin wrote: > >> > Hi Greg, > >> > > >> > Pleae pull commits for Linux 3.18 . > >> > > >> > I've sent a review request for all commits over a week ago and all > >> > comments were addressed. > >> > > >> > > >> > Thanks, > >> > Sasha > >> > > >> > ===== > >> > > >> > > >> > The following changes since commit > >6d05aadb69916b7e6595658fd57821219d16f2e6: > >> > > >> > Linux 3.18.108 (2018-05-02 07:59:55 -0700) > >> > > >> > are available in the Git repository at: > >> > > >> > > >git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git > >tags/for-greg-3.18-19052018 > >> > >> All queued up, thanks. > > > >Also, I would not worry about doing these types of backports to 3.18.y > >anymore, unless you notice something really obviously broken that gets > >fixed up, as I'm trying to wind this kernel tree down. > > *cries in Android OEM neglect* I feel for you :( > > Turns out that > >very few people are actually using it, so I don't want to waste > >people's > >time on it. > > Qualcomm's general neglect of linux-stable hasn't helped things here > :( Here's to hoping things get better along the line... I think it has. Looks like 4.4.y and 4.9.y are getting merged into Qualcomm's trees. And supposidly 3.18.y is as well, but I do not see _any_ device updating their 3.18.y kernel "in the wild" as I do not think any OEM cares about their 3.18.y based devices anymore :( For 4.4.y, it looks better, I am finally seeing updates happen, so while things are not where I would like to see them, it's better than it was a year ago. thanks, greg k-h
