Re: [PATCH 3.18 00/47] 3.18.132-stable review

[Harsh Shandilya]

On 11 January 2019 7:37:45 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.132 release.
>There are 47 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Jan 13 13:09:31 UTC 2019.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.132-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the OnePlus 3, no userspace regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/88] 4.4.170-stable review

[Harsh Shandilya]

On 11 January 2019 7:37:29 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.4.170 release.
>There are 88 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Jan 13 13:09:58 UTC 2019.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.170-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.4.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Pixel 2, no userspace or dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 00/46] 4.19.13-stable review

[Harsh Shandilya]

On 28 December 2018 5:21:54 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.13 release.
>There are 46 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Dec 30 11:30:49 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.13-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 00/44] 4.19.11-stable review

[Harsh Shandilya]

On 18 December 2018 10:09:12 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.11 release.
>There are 44 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Dec 20 16:39:02 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.11-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/142] 4.19.10-stable review

[Harsh Shandilya]

On 14 December 2018 5:28:05 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.10 release.
>There are 142 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Dec 16 11:57:12 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.10-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/88] 4.4.168-stable review

[Harsh Shandilya]

On 14 December 2018 5:29:34 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.4.168 release.
>There are 88 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Dec 16 11:56:41 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.168-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.4.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Pixel 2, no dmesg regressions. Rather clean merge, only 
required adjustments in two places in Qualcomm drivers for the get_user_pages 
API change.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/91] 4.4.167-stable review

[Harsh Shandilya]

On 11 December 2018 9:10:19 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.4.167 release.
>There are 91 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Dec 13 15:15:44 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.167-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.4.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Merged and build tested using GCC 7.3.1, GCC 8.2.1 and Clang 8.0.6 with 
-Werror, no build or dmesg regressions on the Pixel 2.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/139] 4.19.7-stable review

[Harsh Shandilya]

On 4 December 2018 4:18:01 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.7 release.
>There are 139 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Dec  6 10:36:22 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.7-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Peachy as usual on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/139] 4.19.7-stable review

[Harsh Shandilya]

On 4 December 2018 4:18:01 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.7 release.
>There are 139 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Dec  6 10:36:22 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.7-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Peachy as usual on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/110] 4.19.6-stable review

[Harsh Shandilya]

On 30 November 2018 12:47:52 PM IST, Greg Kroah-Hartman 
 wrote:
>On Fri, Nov 30, 2018 at 03:54:48AM +0530, Harsh Shandilya wrote:
>> On 29 November 2018 7:41:31 PM IST, Greg Kroah-Hartman
> wrote:
>> >This is the start of the stable review cycle for the 4.19.6 release.
>> >There are 110 patches in this series, all will be posted as a
>response
>> >to this one.  If anyone has any issues with these being applied,
>please
>> >let me know.
>> >
>> >Responses should be made by Sat Dec  1 13:58:54 UTC 2018.
>> >Anything received after that time might be too late.
>> >
>> >The whole patch series can be found in one patch at:
>>
>>  
>> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.6-rc1.gz
>> >or in the git tree and branch at:
>>
>>  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>> >linux-4.19.y
>> >and the diffstat can be found below.
>> >
>> >thanks,
>> >
>> >greg k-h
>> Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg
>regressions.
>
>Thanks for testing these and letting me know.
>
>> P.S. My GCC loving friend Gabe said hi :p
>
>People love gcc?  :)
>
>greg k-h

Everybody's got their thing, I'm not one to judge /shrug 
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/110] 4.19.6-stable review

[Harsh Shandilya]

On 30 November 2018 12:47:52 PM IST, Greg Kroah-Hartman 
 wrote:
>On Fri, Nov 30, 2018 at 03:54:48AM +0530, Harsh Shandilya wrote:
>> On 29 November 2018 7:41:31 PM IST, Greg Kroah-Hartman
> wrote:
>> >This is the start of the stable review cycle for the 4.19.6 release.
>> >There are 110 patches in this series, all will be posted as a
>response
>> >to this one.  If anyone has any issues with these being applied,
>please
>> >let me know.
>> >
>> >Responses should be made by Sat Dec  1 13:58:54 UTC 2018.
>> >Anything received after that time might be too late.
>> >
>> >The whole patch series can be found in one patch at:
>>
>>  
>> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.6-rc1.gz
>> >or in the git tree and branch at:
>>
>>  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>> >linux-4.19.y
>> >and the diffstat can be found below.
>> >
>> >thanks,
>> >
>> >greg k-h
>> Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg
>regressions.
>
>Thanks for testing these and letting me know.
>
>> P.S. My GCC loving friend Gabe said hi :p
>
>People love gcc?  :)
>
>greg k-h

Everybody's got their thing, I'm not one to judge /shrug 
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/110] 4.19.6-stable review

[Harsh Shandilya]

On 29 November 2018 7:41:31 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.6 release.
>There are 110 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat Dec  1 13:58:54 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.6-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.

P.S. My GCC loving friend Gabe said hi :p
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/110] 4.19.6-stable review

[Harsh Shandilya]

On 29 November 2018 7:41:31 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.6 release.
>There are 110 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat Dec  1 13:58:54 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.6-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.

P.S. My GCC loving friend Gabe said hi :p
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/86] 4.4.166-stable review

[Harsh Shandilya]

lwifi/mvm/mac80211.c  |  12 +-
> drivers/net/wireless/iwlwifi/mvm/nvm.c   |   5 +-
> drivers/net/wireless/mwifiex/cfg80211.c  |  10 +-
> drivers/net/wireless/mwifiex/wmm.c   |  12 +-
> drivers/nfc/nfcmrvl/uart.c   |   5 +-
> drivers/of/base.c|  25 +
> drivers/scsi/qla2xxx/qla_os.c|   5 +
> drivers/scsi/ufs/ufs.h   |   3 +-
> drivers/scsi/ufs/ufshcd-pci.c|   2 +
> drivers/scsi/ufs/ufshcd-pltfrm.c |   5 +-
> drivers/scsi/ufs/ufshcd.c|  75 ++-
> drivers/tty/n_tty.c  |  19 +-
> drivers/tty/tty_buffer.c |   2 +
> drivers/usb/core/hub.c   |   4 +-
> drivers/usb/host/xhci-hub.c  |  66 ++-
> drivers/usb/host/xhci-ring.c |   2 +-
> drivers/usb/host/xhci.h  |   2 +-
> fs/9p/vfs_dir.c  |  11 -
> fs/bfs/inode.c   |   9 +-
> fs/btrfs/extent-tree.c   |  10 +-
> fs/btrfs/ioctl.c |  11 +-
> fs/gfs2/ops_fstype.c |   2 +-
> fs/namei.c   |  53 +-
> include/linux/can/dev.h  |   1 +
> include/linux/fs.h   |   2 +
> include/linux/of.h   |   8 +
> kernel/debug/kdb/kdb_io.c|  15 +-
> kernel/debug/kdb/kdb_private.h   |   2 +-
> kernel/debug/kdb/kdb_support.c   |  10 +-
> kernel/sched/core.c  |   4 +-
> kernel/sysctl.c  |  18 +
> mm/shmem.c   |   4 +-
> net/llc/af_llc.c |  11 +-
> net/netfilter/nf_tables_api.c|   1 +
> net/sctp/associola.c |  10 +-
> net/sunrpc/auth_generic.c|   8 +-
> 57 files changed, 1126 insertions(+), 343 deletions(-)

Built and booted on the Pixel 2, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/86] 4.4.166-stable review

[Harsh Shandilya]

lwifi/mvm/mac80211.c  |  12 +-
> drivers/net/wireless/iwlwifi/mvm/nvm.c   |   5 +-
> drivers/net/wireless/mwifiex/cfg80211.c  |  10 +-
> drivers/net/wireless/mwifiex/wmm.c   |  12 +-
> drivers/nfc/nfcmrvl/uart.c   |   5 +-
> drivers/of/base.c|  25 +
> drivers/scsi/qla2xxx/qla_os.c|   5 +
> drivers/scsi/ufs/ufs.h   |   3 +-
> drivers/scsi/ufs/ufshcd-pci.c|   2 +
> drivers/scsi/ufs/ufshcd-pltfrm.c |   5 +-
> drivers/scsi/ufs/ufshcd.c|  75 ++-
> drivers/tty/n_tty.c  |  19 +-
> drivers/tty/tty_buffer.c |   2 +
> drivers/usb/core/hub.c   |   4 +-
> drivers/usb/host/xhci-hub.c  |  66 ++-
> drivers/usb/host/xhci-ring.c |   2 +-
> drivers/usb/host/xhci.h  |   2 +-
> fs/9p/vfs_dir.c  |  11 -
> fs/bfs/inode.c   |   9 +-
> fs/btrfs/extent-tree.c   |  10 +-
> fs/btrfs/ioctl.c |  11 +-
> fs/gfs2/ops_fstype.c |   2 +-
> fs/namei.c   |  53 +-
> include/linux/can/dev.h  |   1 +
> include/linux/fs.h   |   2 +
> include/linux/of.h   |   8 +
> kernel/debug/kdb/kdb_io.c|  15 +-
> kernel/debug/kdb/kdb_private.h   |   2 +-
> kernel/debug/kdb/kdb_support.c   |  10 +-
> kernel/sched/core.c  |   4 +-
> kernel/sysctl.c  |  18 +
> mm/shmem.c   |   4 +-
> net/llc/af_llc.c |  11 +-
> net/netfilter/nf_tables_api.c|   1 +
> net/sctp/associola.c |  10 +-
> net/sunrpc/auth_generic.c|   8 +-
> 57 files changed, 1126 insertions(+), 343 deletions(-)

Built and booted on the Pixel 2, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/83] 3.18.128-stable review

[Harsh Shandilya]

On 29 November 2018 7:41:18 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.128 release.
>There are 83 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat Dec  1 14:01:23 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.128-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the OnePlus 3T, no immediate regressions noticed.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/83] 3.18.128-stable review

[Harsh Shandilya]

On 29 November 2018 7:41:18 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.128 release.
>There are 83 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat Dec  1 14:01:23 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.128-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the OnePlus 3T, no immediate regressions noticed.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/118] 4.19.5-stable review

[Harsh Shandilya]

On 26 November 2018 4:19:54 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.5 release.
>There are 118 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 28 10:50:22 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.5-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/118] 4.19.5-stable review

[Harsh Shandilya]

On 26 November 2018 4:19:54 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.5 release.
>There are 118 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 28 10:50:22 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.5-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/70] 4.4.165-stable review

[Harsh Shandilya]

On 26 November 2018 4:20:15 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.4.165 release.
>There are 70 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 28 10:50:16 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.165-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.4.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
A rather painful merge into the Pixel 2 tree but I'm glad to report I have 
noticed no regressions over the past couple hours of testing.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.4 00/70] 4.4.165-stable review

[Harsh Shandilya]

On 26 November 2018 4:20:15 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.4.165 release.
>There are 70 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 28 10:50:16 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.165-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.4.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
A rather painful merge into the Pixel 2 tree but I'm glad to report I have 
noticed no regressions over the past couple hours of testing.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/24] 3.18.127-stable review

[Harsh Shandilya]

On 26 November 2018 4:20:54 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.127 release.
>There are 24 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 28 10:50:13 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.127-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the OnePlus 3T, no immediate regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/24] 3.18.127-stable review

[Harsh Shandilya]

On 26 November 2018 4:20:54 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.127 release.
>There are 24 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 28 10:50:13 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.127-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the OnePlus 3T, no immediate regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 00/42] 4.19.4-stable review

[Harsh Shandilya]

On 22 November 2018 12:35:36 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.4 release.
>There are 42 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Fri Nov 23 18:31:31 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.4-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 00/42] 4.19.4-stable review

[Harsh Shandilya]

On 22 November 2018 12:35:36 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.4 release.
>There are 42 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Fri Nov 23 18:31:31 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.4-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Built and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/90] 3.18.126-stable review

[Harsh Shandilya]

On 19 November 2018 9:58:42 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.126 release.
>There are 90 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 21 16:25:28 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.126-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Peachy as always on the OnePlus 3(T).

P.S. Not tired of this old-ass tree yet? :P
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/90] 3.18.126-stable review

[Harsh Shandilya]

On 19 November 2018 9:58:42 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.126 release.
>There are 90 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 21 16:25:28 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.126-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Peachy as always on the OnePlus 3(T).

P.S. Not tired of this old-ass tree yet? :P
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/205] 4.19.3-stable review

[Harsh Shandilya]

On 19 November 2018 9:55:07 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.3 release.
>There are 205 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 21 16:24:55 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.3-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
>
Compiled and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 4.19 000/205] 4.19.3-stable review

[Harsh Shandilya]

On 19 November 2018 9:55:07 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 4.19.3 release.
>There are 205 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed Nov 21 16:24:55 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.3-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-4.19.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
>
Compiled and booted on the Lenovo IdeaPad 330-15ARR, no dmesg regressions.
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/29] 3.18.122-stable review

[Harsh 'Shandilya]

On 8 September 2018 2:40:21 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.122 release.
>There are 29 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Sep  9 21:08:52 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.122-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Cleanly merges and builds with Werror in my oneplus3 tree. No immediate 
regressions noticed. Thanks for the update.
--
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/29] 3.18.122-stable review

[Harsh 'Shandilya]

On 8 September 2018 2:40:21 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.122 release.
>There are 29 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Sep  9 21:08:52 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.122-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Cleanly merges and builds with Werror in my oneplus3 tree. No immediate 
regressions noticed. Thanks for the update.
--
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/15] 3.18.119-stable review

[Harsh 'Shandilya]

On 17 August 2018 12:11:37 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.119 release.
>There are 15 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat Aug 18 17:16:20 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.119-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
Merged cleanly and compiled with -Werror, All good on the OnePlus 3T. Thanks 
for the update!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/15] 3.18.119-stable review

[Harsh 'Shandilya]

On 17 August 2018 12:11:37 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.119 release.
>There are 15 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat Aug 18 17:16:20 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.119-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
Merged cleanly and compiled with -Werror, All good on the OnePlus 3T. Thanks 
for the update!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/23] 3.18.115-stable review

[Harsh 'Shandilya]

On 10 July 2018 11:54:33 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.115 release.
>There are 23 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Jul 12 18:22:59 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.115-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

 Builds with -Werror and boots fine on the OnePlus3T, no immediate regressions 
noticed. Thanks for the update!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/23] 3.18.115-stable review

[Harsh 'Shandilya]

On 10 July 2018 11:54:33 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.115 release.
>There are 23 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Jul 12 18:22:59 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.115-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

 Builds with -Werror and boots fine on the OnePlus3T, no immediate regressions 
noticed. Thanks for the update!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/21] 3.18.113-stable review

[Harsh Shandilya]

On 12 June 2018 10:21:57 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.113 release.
>There are 21 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Jun 14 16:48:15 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Merged, compiled and flashed on the OnePlus 3T, no immediate regressions 
noticed. Thanks for the update!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/21] 3.18.113-stable review

[Harsh Shandilya]

On 12 June 2018 10:21:57 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.113 release.
>There are 21 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Thu Jun 14 16:48:15 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Merged, compiled and flashed on the OnePlus 3T, no immediate regressions 
noticed. Thanks for the update!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 000/185] 3.18.111-stable review

[Harsh Shandilya]

On 28 May 2018 3:30:41 PM IST, Greg Kroah-Hartman <gre...@linuxfoundation.org> 
wrote:
>This is the start of the stable review cycle for the 3.18.111 release.
>There are 185 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed May 30 10:00:18 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.111-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.

Merged and flashed onto the OnePlus 3T, no regressions noticed so far. Thanks 
for the update!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 000/185] 3.18.111-stable review

[Harsh Shandilya]

On 28 May 2018 3:30:41 PM IST, Greg Kroah-Hartman  
wrote:
>This is the start of the stable review cycle for the 3.18.111 release.
>There are 185 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed May 30 10:00:18 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.111-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.

Merged and flashed onto the OnePlus 3T, no regressions noticed so far. Thanks 
for the update!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/45] 3.18.110-stable review

[Harsh Shandilya]

On 24 May 2018 3:08:08 PM IST, Greg Kroah-Hartman <gre...@linuxfoundation.org> 
wrote:
>This is the start of the stable review cycle for the 3.18.110 release.
>There are 45 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat May 26 09:30:59 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.110-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.

Cleanly merges, builds and boots on the OnePlus 3T, no immediate regressions 
noticed. Thanks for the update!
-- 
Harsh Shandilya, PRJKT Development LLC.

Re: [PATCH 3.18 00/45] 3.18.110-stable review

[Harsh Shandilya]

On 24 May 2018 3:08:08 PM IST, Greg Kroah-Hartman  
wrote:
>This is the start of the stable review cycle for the 3.18.110 release.
>There are 45 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sat May 26 09:30:59 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.110-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.

Cleanly merges, builds and boots on the OnePlus 3T, no immediate regressions 
noticed. Thanks for the update!
-- 
Harsh Shandilya, PRJKT Development LLC.

Re: [PATCH 3.18 00/23] 3.18.109-stable review

[Harsh Shandilya]

On 14 May 2018 12:18:29 PM IST, Greg Kroah-Hartman <gre...@linuxfoundation.org> 
wrote:
>This is the start of the stable review cycle for the 3.18.109 release.
>There are 23 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed May 16 06:46:49 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.109-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

Merged and compiled on my OnePlus 3T, no immediate regressions. Thanks for the 
update!
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/23] 3.18.109-stable review

[Harsh Shandilya]

On 14 May 2018 12:18:29 PM IST, Greg Kroah-Hartman  
wrote:
>This is the start of the stable review cycle for the 3.18.109 release.
>There are 23 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed May 16 06:46:49 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.109-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

Merged and compiled on my OnePlus 3T, no immediate regressions. Thanks for the 
update!
-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/25] 3.18.108-stable review

[Harsh Shandilya]

On 1 May 2018 12:53:07 AM IST, Greg Kroah-Hartman <gre...@linuxfoundation.org> 
wrote:
>This is the start of the stable review cycle for the 3.18.108 release.
>There are 25 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed May  2 18:39:02 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.108-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Builds and boots on the OnePlus3T, no immediate regressions. Thanks for the 
update!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/25] 3.18.108-stable review

[Harsh Shandilya]

On 1 May 2018 12:53:07 AM IST, Greg Kroah-Hartman  
wrote:
>This is the start of the stable review cycle for the 3.18.108 release.
>There are 25 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Wed May  2 18:39:02 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.108-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Builds and boots on the OnePlus3T, no immediate regressions. Thanks for the 
update!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/24] 3.18.107-stable review

[Harsh Shandilya]

On 28 April 2018 11:21:20 AM IST, Greg Kroah-Hartman 
<gre...@linuxfoundation.org> wrote:
>On Fri, Apr 27, 2018 at 11:00:41PM +0700, Dede Dindin Qudsy wrote:
>> 
>> 
>> On 27/04/18 20:57, Greg Kroah-Hartman wrote:
>> > This is the start of the stable review cycle for the 3.18.107
>release.
>> > There are 24 patches in this series, all will be posted as a
>response
>> > to this one.  If anyone has any issues with these being applied,
>please
>> > let me know.
>> > 
>> > Responses should be made by Sun Apr 29 13:56:20 UTC 2018.
>> > Anything received after that time might be too late.
>> > 
>> > The whole patch series can be found in one patch at:
>> >
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.107-rc1.gz
>> > or in the git tree and branch at:
>> >
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>> > and the diffstat can be found below.
>> > 
>> > thanks,
>> > 
>> > greg k-h
>> 
>> build and tested on rn4, No dmesg regressions.
>
>What is a "rn4"?  Anyway, thanks for testing and letting me know.
>
>greg k-h

Xiaomi Redmi Note 4, most GPL adhering Android OEM ever :P
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/24] 3.18.107-stable review

[Harsh Shandilya]

On 28 April 2018 11:21:20 AM IST, Greg Kroah-Hartman 
 wrote:
>On Fri, Apr 27, 2018 at 11:00:41PM +0700, Dede Dindin Qudsy wrote:
>> 
>> 
>> On 27/04/18 20:57, Greg Kroah-Hartman wrote:
>> > This is the start of the stable review cycle for the 3.18.107
>release.
>> > There are 24 patches in this series, all will be posted as a
>response
>> > to this one.  If anyone has any issues with these being applied,
>please
>> > let me know.
>> > 
>> > Responses should be made by Sun Apr 29 13:56:20 UTC 2018.
>> > Anything received after that time might be too late.
>> > 
>> > The whole patch series can be found in one patch at:
>> >
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.107-rc1.gz
>> > or in the git tree and branch at:
>> >
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>> > and the diffstat can be found below.
>> > 
>> > thanks,
>> > 
>> > greg k-h
>> 
>> build and tested on rn4, No dmesg regressions.
>
>What is a "rn4"?  Anyway, thanks for testing and letting me know.
>
>greg k-h

Xiaomi Redmi Note 4, most GPL adhering Android OEM ever :P
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/24] 3.18.107-stable review

[Harsh Shandilya]

On 27 April 2018 7:27:35 PM IST, Greg Kroah-Hartman 
<gre...@linuxfoundation.org> wrote:
>This is the start of the stable review cycle for the 3.18.107 release.
>There are 24 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Apr 29 13:56:20 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.107-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
No issues on the OnePlus 3, usage seems fine so far. Thanks!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/24] 3.18.107-stable review

[Harsh Shandilya]

On 27 April 2018 7:27:35 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.107 release.
>There are 24 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Apr 29 13:56:20 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.107-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
No issues on the OnePlus 3, usage seems fine so far. Thanks!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.106

[Harsh Shandilya]

On 24 April 2018 2:22:06 PM IST, Greg KH <gre...@linuxfoundation.org> wrote:
>I'm announcing the release of the 3.18.106 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
>thanks,
>
>greg k-h
Status same as -rc1, no merge issues and no regressions. Thanks for the update!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.106

[Harsh Shandilya]

On 24 April 2018 2:22:06 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.106 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
>thanks,
>
>greg k-h
Status same as -rc1, no merge issues and no regressions. Thanks for the update!

-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/52] 3.18.106-stable review

[Harsh Shandilya]

On 22 April 2018 7:23:33 PM IST, Greg Kroah-Hartman 
<gre...@linuxfoundation.org> wrote:
>This is the start of the stable review cycle for the 3.18.106 release.
>There are 52 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Tue Apr 24 13:53:02 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.106-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Builds and boots on the OnePlus3T, no immediate regressions. Good ol' boring 
release :-)
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/52] 3.18.106-stable review

[Harsh Shandilya]

On 22 April 2018 7:23:33 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.106 release.
>There are 52 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Tue Apr 24 13:53:02 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.106-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Builds and boots on the OnePlus3T, no immediate regressions. Good ol' boring 
release :-)
-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.105

[Harsh Shandilya]

On 14 April 2018 1:54:59 AM IST, Greg KH <gre...@linuxfoundation.org> wrote:
>I'm announcing the release of the 3.18.105 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
>thanks,
>
>greg k-h
Just realised I actually forgot to report back here after yesterday's tests, 
insomnia's a bitch.

Everything's hunky dory on the OnePlus3T, clean merge and no regressions 
noticed over the past day. Thanks for your continued work on this!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.105

[Harsh Shandilya]

On 14 April 2018 1:54:59 AM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.105 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
>thanks,
>
>greg k-h
Just realised I actually forgot to report back here after yesterday's tests, 
insomnia's a bitch.

Everything's hunky dory on the OnePlus3T, clean merge and no regressions 
noticed over the past day. Thanks for your continued work on this!
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH] Revert "xhci: plat: Register shutdown for xhci_plat"

[Harsh Shandilya]

On 13 April 2018 11:51:28 AM IST, Greg Kroah-Hartman 
<gre...@linuxfoundation.org> wrote:
>On Fri, Apr 13, 2018 at 08:12:31AM +0530, Harsh Shandilya wrote:
>> On 13 April 2018 5:59:51 AM IST, Greg Hackmann <ghackm...@google.com>
>wrote:
>> >Pixel 2 field testers reported that when they tried to reboot their
>> >phones with some USB devices plugged in, the reboot would get wedged
>> >and
>> >eventually trigger watchdog reset.  Once the Pixel kernel team found
>a
>> >reliable repro case, they narrowed it down to this commit's 4.4.y
>> >backport.  Reverting the change made the issue go away.
>> 
>> Are you allowed to make the repro steps public? I'm writing this from
>> a walleye and would be grateful if I could test for this in the
>> modifed tree I'm running atm.  -- 
>
>I was told the steps are pretty simple:
>   - reboot the phone a lot
>eventually it will hang.  There's a fix in the code aurora kernel tree
>for this that they never sent upstream for some odd reason (they sent
>the first patch, why not the second?)
>
>I'll go revert this for now, thanks for the patch!
>
>greg k-h

That'd make sense, I only tried rebooting like five times before I had to run 
for a class.

As far as CAF is concerned, I feel the not submitting upstream, working extra 
to write patches which have usually better variants already upstream, seems to 
be common. All USB changes were dropped when they merged kernel-common into 
msm-3.18 with no real explanation which has been an annoyance more than once 
during merging -stable in my fork of msm-3.18. While I understand their 
situation of maintaining upwards of 5 million lines of code not upstream, it 
still feels sloppy to not merge stable updates and do extra work instead. /* 
End rant */
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH] Revert "xhci: plat: Register shutdown for xhci_plat"

[Harsh Shandilya]

On 13 April 2018 11:51:28 AM IST, Greg Kroah-Hartman 
 wrote:
>On Fri, Apr 13, 2018 at 08:12:31AM +0530, Harsh Shandilya wrote:
>> On 13 April 2018 5:59:51 AM IST, Greg Hackmann 
>wrote:
>> >Pixel 2 field testers reported that when they tried to reboot their
>> >phones with some USB devices plugged in, the reboot would get wedged
>> >and
>> >eventually trigger watchdog reset.  Once the Pixel kernel team found
>a
>> >reliable repro case, they narrowed it down to this commit's 4.4.y
>> >backport.  Reverting the change made the issue go away.
>> 
>> Are you allowed to make the repro steps public? I'm writing this from
>> a walleye and would be grateful if I could test for this in the
>> modifed tree I'm running atm.  -- 
>
>I was told the steps are pretty simple:
>   - reboot the phone a lot
>eventually it will hang.  There's a fix in the code aurora kernel tree
>for this that they never sent upstream for some odd reason (they sent
>the first patch, why not the second?)
>
>I'll go revert this for now, thanks for the patch!
>
>greg k-h

That'd make sense, I only tried rebooting like five times before I had to run 
for a class.

As far as CAF is concerned, I feel the not submitting upstream, working extra 
to write patches which have usually better variants already upstream, seems to 
be common. All USB changes were dropped when they merged kernel-common into 
msm-3.18 with no real explanation which has been an annoyance more than once 
during merging -stable in my fork of msm-3.18. While I understand their 
situation of maintaining upwards of 5 million lines of code not upstream, it 
still feels sloppy to not merge stable updates and do extra work instead. /* 
End rant */
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH] Revert "xhci: plat: Register shutdown for xhci_plat"

[Harsh Shandilya]

On 13 April 2018 5:59:51 AM IST, Greg Hackmann <ghackm...@google.com> wrote:
>Pixel 2 field testers reported that when they tried to reboot their
>phones with some USB devices plugged in, the reboot would get wedged
>and
>eventually trigger watchdog reset.  Once the Pixel kernel team found a
>reliable repro case, they narrowed it down to this commit's 4.4.y
>backport.  Reverting the change made the issue go away.

Are you allowed to make the repro steps public? I'm writing this from a walleye 
and would be grateful if I could test for this in the modifed tree I'm running 
atm. 
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH] Revert "xhci: plat: Register shutdown for xhci_plat"

[Harsh Shandilya]

On 13 April 2018 5:59:51 AM IST, Greg Hackmann  wrote:
>Pixel 2 field testers reported that when they tried to reboot their
>phones with some USB devices plugged in, the reboot would get wedged
>and
>eventually trigger watchdog reset.  Once the Pixel kernel team found a
>reliable repro case, they narrowed it down to this commit's 4.4.y
>backport.  Reverting the change made the issue go away.

Are you allowed to make the repro steps public? I'm writing this from a walleye 
and would be grateful if I could test for this in the modifed tree I'm running 
atm. 
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 000/121] 3.18.105-stable review

[Harsh Shandilya]

On 12 April 2018 12:05:03 AM IST, Greg Kroah-Hartman 
<gre...@linuxfoundation.org> wrote:
>This is the start of the stable review cycle for the 3.18.105 release.
>There are 121 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Fri Apr 13 18:34:28 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.105-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Builds and boots on the OnePlus3T, no immediate regressions noticed, clean 
merge into msm-3.18. Thanks for the update :)
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 000/121] 3.18.105-stable review

[Harsh Shandilya]

On 12 April 2018 12:05:03 AM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.105 release.
>There are 121 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Fri Apr 13 18:34:28 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.105-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h
Builds and boots on the OnePlus3T, no immediate regressions noticed, clean 
merge into msm-3.18. Thanks for the update :)
-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.104

[Harsh Shandilya]

On 10 April 2018 12:43:46 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.104 kernel.
>
>Only users who had build errors in 3.18.103 need to upgrade, this is a
>single-bugfix-only release.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary


OnePlus3T doesn't use the fec so nothing there to really test, but this builds 
fine.

>thanks,
>
>greg k-h
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: Linux 3.18.104

[Harsh Shandilya]

On 10 April 2018 12:43:46 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.104 kernel.
>
>Only users who had build errors in 3.18.103 need to upgrade, this is a
>single-bugfix-only release.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary


OnePlus3T doesn't use the fec so nothing there to really test, but this builds 
fine.

>thanks,
>
>greg k-h
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: Linux 3.18.103

[Harsh Shandilya]

On 8 April 2018 8:37:08 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.103 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

Builds and boots on the OnePlus3T, running it for the past few hours with no 
visible regressions.

>thanks,
>
>greg k-h

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: Linux 3.18.103

[Harsh Shandilya]

On 8 April 2018 8:37:08 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.103 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

Builds and boots on the OnePlus3T, running it for the past few hours with no 
visible regressions.

>thanks,
>
>greg k-h

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [PATCH 3.18 00/93] 3.18.103-stable review

[Harsh Shandilya]

On 6 April 2018 6:52:29 PM IST, Greg Kroah-Hartman <gre...@linuxfoundation.org> 
wrote:
>This is the start of the stable review cycle for the 3.18.103 release.
>There are 93 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Apr  8 08:42:04 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.103-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

Builds and boots on the OnePlus3T, no visible regressions. The merge was 
slightly gnarly with "proc: revert /proc//maps [stack:TID] annotation" 
conflicting due to kernel-common changes and the v4l2 series conflicting with 
CAF changes in the msm-3.18 tree.

Thanks,

Harsh Shandilya

Re: [PATCH 3.18 00/93] 3.18.103-stable review

[Harsh Shandilya]

On 6 April 2018 6:52:29 PM IST, Greg Kroah-Hartman  
wrote:
>This is the start of the stable review cycle for the 3.18.103 release.
>There are 93 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Apr  8 08:42:04 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.103-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

Builds and boots on the OnePlus3T, no visible regressions. The merge was 
slightly gnarly with "proc: revert /proc//maps [stack:TID] annotation" 
conflicting due to kernel-common changes and the v4l2 series conflicting with 
CAF changes in the msm-3.18 tree.

Thanks,

Harsh Shandilya

Re: Linux 3.18.102

[Harsh Shandilya]

On 25 March 2018 2:29:52 PM IST, Greg KH <gre...@linuxfoundation.org> wrote:
>I'm announcing the release of the 3.18.102 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
Builds and boots on the OnePlus3T, no regressions noticed so far. Thanks!

>thanks,
>
>greg k-h

-- 
Harsh Shandilya
PRJKT Development LLC

Re: Linux 3.18.102

[Harsh Shandilya]

On 25 March 2018 2:29:52 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.102 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
Builds and boots on the OnePlus3T, no regressions noticed so far. Thanks!

>thanks,
>
>greg k-h

-- 
Harsh Shandilya
PRJKT Development LLC

Re: [PATCH 3.18 00/47] 3.18.102-stable review

[Harsh Shandilya]

On 23 March 2018 3:24:51 PM IST, Greg Kroah-Hartman 
<gre...@linuxfoundation.org> wrote:
>This is the start of the stable review cycle for the 3.18.102 release.
>There are 47 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Mar 25 09:42:36 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.102-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

Builds and boots on the OnePlus3T, no regressions noticed so far. Slight merge 
issue in GPU drivers due to CAF changes, kernel-common should merge without a 
problem.
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 3.18 00/47] 3.18.102-stable review

[Harsh Shandilya]

On 23 March 2018 3:24:51 PM IST, Greg Kroah-Hartman 
 wrote:
>This is the start of the stable review cycle for the 3.18.102 release.
>There are 47 patches in this series, all will be posted as a response
>to this one.  If anyone has any issues with these being applied, please
>let me know.
>
>Responses should be made by Sun Mar 25 09:42:36 UTC 2018.
>Anything received after that time might be too late.
>
>The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.102-rc1.gz
>or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>linux-3.18.y
>and the diffstat can be found below.
>
>thanks,
>
>greg k-h

Builds and boots on the OnePlus3T, no regressions noticed so far. Slight merge 
issue in GPU drivers due to CAF changes, kernel-common should merge without a 
problem.
-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.101

[Harsh Shandilya]

On 22 March 2018 2:33:42 PM IST, Greg KH <gre...@linuxfoundation.org> wrote:
>I'm announcing the release of the 3.18.101 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

Builds and boots on the OnePlus3T, no immediate regressions noticed.
-- 
Harsh Shandilya, PRJKT Development LLC

Re: Linux 3.18.101

[Harsh Shandilya]

On 22 March 2018 2:33:42 PM IST, Greg KH  wrote:
>I'm announcing the release of the 3.18.101 kernel.
>
>All users of the 3.18 kernel series must upgrade.
>
>The updated 3.18.y git tree can be found at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>linux-3.18.y
>and can be browsed at the normal kernel.org git web browser:
>   
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

Builds and boots on the OnePlus3T, no immediate regressions noticed.
-- 
Harsh Shandilya, PRJKT Development LLC

Re: [PATCH 1/1] Bluetooth: Set HCI_QUIRK_SIMULTANEOUS_DISCOVERY for BTUSB_QCA_ROME

[Harsh Shandilya]

On 21 March 2018 9:54:37 PM IST, Greg KH  wrote:
>On Wed, Mar 21, 2018 at 09:09:57AM -0700, Vic Wei wrote:
>> QCA Rome controllers can do both LE scan and BR/EDR inquiry at once.
>> 
>> Change-Id: I89e1412d635f4cd7b2500f7492f37430ea139f0c
>
>What is this line for?

That's the Change ID required by everything that goes through Gerrit. CAF (I'm 
assuming Vic is from CodeAurora Forums judging by the email) uses Gerrit as 
their review platform for the Android for MSM project.

Re: [PATCH 1/1] Bluetooth: Set HCI_QUIRK_SIMULTANEOUS_DISCOVERY for BTUSB_QCA_ROME

[Harsh Shandilya]

On 21 March 2018 9:54:37 PM IST, Greg KH  wrote:
>On Wed, Mar 21, 2018 at 09:09:57AM -0700, Vic Wei wrote:
>> QCA Rome controllers can do both LE scan and BR/EDR inquiry at once.
>> 
>> Change-Id: I89e1412d635f4cd7b2500f7492f37430ea139f0c
>
>What is this line for?

That's the Change ID required by everything that goes through Gerrit. CAF (I'm 
assuming Vic is from CodeAurora Forums judging by the email) uses Gerrit as 
their review platform for the Android for MSM project.

[PATCH 2/2] drivers: android: Fix logtags in methods

[Harsh Shandilya]

From: Harsh Shandilya <ha...@prjkt.io>

Several methods in the driver were hardcoding
the function name in their logging calls which
is a checkpatch violation. Utilise the __func__
macro to avoid needing to add the function name
as is to the string.

Test: logtags in dmesg remain unaffected before
and after the patch.

Signed-off-by: Harsh Shandilya <ha...@prjkt.io>

Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: "Arve Hjønnevåg" <a...@android.com>
Cc: Todd Kjos <tk...@android.com>
Cc: Martijn Coenen <m...@android.com>
Cc: de...@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org
---
 drivers/android/binder.c | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index ffb31dd9191a..1e48acfe27b7 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -4467,8 +4467,8 @@ static long binder_ioctl(struct file *filp, unsigned int 
cmd, unsigned long arg)
unsigned int size = _IOC_SIZE(cmd);
void __user *ubuf = (void __user *)arg;
 
-   /*pr_info("binder_ioctl: %d:%d %x %lx\n",
-   proc->pid, current->pid, cmd, arg);*/
+   // pr_info("%s: %d:%d %x %lx\n",
+   //  __func__, proc->pid, current->pid, cmd, arg);
 
binder_selftest_alloc(>alloc);
 
@@ -4631,8 +4631,9 @@ static int binder_mmap(struct file *filp, struct 
vm_area_struct *vma)
return 0;
 
 err_bad_arg:
-   pr_err("binder_mmap: %d %lx-%lx %s failed %d\n",
-  proc->pid, vma->vm_start, vma->vm_end, failure_string, ret);
+   pr_err("%s: %d %lx-%lx %s failed %d\n",
+   __func__, proc->pid, vma->vm_start, vma->vm_end,
+   failure_string, ret);
return ret;
 }
 
@@ -4641,8 +4642,8 @@ static int binder_open(struct inode *nodp, struct file 
*filp)
struct binder_proc *proc;
struct binder_device *binder_dev;
 
-   binder_debug(BINDER_DEBUG_OPEN_CLOSE, "binder_open: %d:%d\n",
-current->group_leader->pid, current->pid);
+   binder_debug(BINDER_DEBUG_OPEN_CLOSE, "%s: %d:%d\n",
+   __func__, current->group_leader->pid, current->pid);
 
proc = kzalloc(sizeof(*proc), GFP_KERNEL);
if (proc == NULL)
-- 
2.15.0.631.g7ddcec0

[PATCH 2/2] drivers: android: Fix logtags in methods

[Harsh Shandilya]

From: Harsh Shandilya 

Several methods in the driver were hardcoding
the function name in their logging calls which
is a checkpatch violation. Utilise the __func__
macro to avoid needing to add the function name
as is to the string.

Test: logtags in dmesg remain unaffected before
and after the patch.

Signed-off-by: Harsh Shandilya 

Cc: Greg Kroah-Hartman 
Cc: "Arve Hjønnevåg" 
Cc: Todd Kjos 
Cc: Martijn Coenen 
Cc: de...@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org
---
 drivers/android/binder.c | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index ffb31dd9191a..1e48acfe27b7 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -4467,8 +4467,8 @@ static long binder_ioctl(struct file *filp, unsigned int 
cmd, unsigned long arg)
unsigned int size = _IOC_SIZE(cmd);
void __user *ubuf = (void __user *)arg;
 
-   /*pr_info("binder_ioctl: %d:%d %x %lx\n",
-   proc->pid, current->pid, cmd, arg);*/
+   // pr_info("%s: %d:%d %x %lx\n",
+   //  __func__, proc->pid, current->pid, cmd, arg);
 
binder_selftest_alloc(>alloc);
 
@@ -4631,8 +4631,9 @@ static int binder_mmap(struct file *filp, struct 
vm_area_struct *vma)
return 0;
 
 err_bad_arg:
-   pr_err("binder_mmap: %d %lx-%lx %s failed %d\n",
-  proc->pid, vma->vm_start, vma->vm_end, failure_string, ret);
+   pr_err("%s: %d %lx-%lx %s failed %d\n",
+   __func__, proc->pid, vma->vm_start, vma->vm_end,
+   failure_string, ret);
return ret;
 }
 
@@ -4641,8 +4642,8 @@ static int binder_open(struct inode *nodp, struct file 
*filp)
struct binder_proc *proc;
struct binder_device *binder_dev;
 
-   binder_debug(BINDER_DEBUG_OPEN_CLOSE, "binder_open: %d:%d\n",
-current->group_leader->pid, current->pid);
+   binder_debug(BINDER_DEBUG_OPEN_CLOSE, "%s: %d:%d\n",
+   __func__, current->group_leader->pid, current->pid);
 
proc = kzalloc(sizeof(*proc), GFP_KERNEL);
if (proc == NULL)
-- 
2.15.0.631.g7ddcec0

[PATCH 1/2] drivers: android: Use octal permissions

[Harsh Shandilya]

From: Harsh Shandilya <ha...@prjkt.io>

checkpatch warns against the use of symbolic permissions,
this patch migrates all symbolic permissions in the binder
driver to octal permissions.

Test: debugfs nodes created by binder have the same unix
permissions prior to and after this patch was applied.

Signed-off-by: Harsh Shandilya <ha...@prjkt.io>

Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: "Arve Hjønnevåg" <a...@android.com>
Cc: Todd Kjos <tk...@android.com>
Cc: Martijn Coenen <m...@android.com>
Cc: de...@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org

---
 drivers/android/binder.c | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index bccec9de0533..ffb31dd9191a 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -141,7 +141,7 @@ enum {
 };
 static uint32_t binder_debug_mask = BINDER_DEBUG_USER_ERROR |
BINDER_DEBUG_FAILED_TRANSACTION | BINDER_DEBUG_DEAD_TRANSACTION;
-module_param_named(debug_mask, binder_debug_mask, uint, S_IWUSR | S_IRUGO);
+module_param_named(debug_mask, binder_debug_mask, uint, 0644);
 
 static char *binder_devices_param = CONFIG_ANDROID_BINDER_DEVICES;
 module_param_named(devices, binder_devices_param, charp, 0444);
@@ -160,7 +160,7 @@ static int binder_set_stop_on_user_error(const char *val,
return ret;
 }
 module_param_call(stop_on_user_error, binder_set_stop_on_user_error,
-   param_get_int, _stop_on_user_error, S_IWUSR | S_IRUGO);
+   param_get_int, _stop_on_user_error, 0644);
 
 #define binder_debug(mask, x...) \
do { \
@@ -4679,7 +4679,7 @@ static int binder_open(struct inode *nodp, struct file 
*filp)
 * anyway print all contexts that a given PID has, so this
 * is not a problem.
 */
-   proc->debugfs_entry = debugfs_create_file(strbuf, S_IRUGO,
+   proc->debugfs_entry = debugfs_create_file(strbuf, 0444,
binder_debugfs_dir_entry_proc,
(void *)(unsigned long)proc->pid,
_proc_fops);
@@ -5518,27 +5518,27 @@ static int __init binder_init(void)
 
if (binder_debugfs_dir_entry_root) {
debugfs_create_file("state",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
NULL,
_state_fops);
debugfs_create_file("stats",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
NULL,
_stats_fops);
debugfs_create_file("transactions",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
NULL,
_transactions_fops);
debugfs_create_file("transaction_log",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
_transaction_log,
_transaction_log_fops);
debugfs_create_file("failed_transaction_log",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
_transaction_log_failed,
_transaction_log_fops);
-- 
2.15.0.631.g7ddcec0

[PATCH 1/2] drivers: android: Use octal permissions

[Harsh Shandilya]

From: Harsh Shandilya 

checkpatch warns against the use of symbolic permissions,
this patch migrates all symbolic permissions in the binder
driver to octal permissions.

Test: debugfs nodes created by binder have the same unix
permissions prior to and after this patch was applied.

Signed-off-by: Harsh Shandilya 

Cc: Greg Kroah-Hartman 
Cc: "Arve Hjønnevåg" 
Cc: Todd Kjos 
Cc: Martijn Coenen 
Cc: de...@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org

---
 drivers/android/binder.c | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index bccec9de0533..ffb31dd9191a 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -141,7 +141,7 @@ enum {
 };
 static uint32_t binder_debug_mask = BINDER_DEBUG_USER_ERROR |
BINDER_DEBUG_FAILED_TRANSACTION | BINDER_DEBUG_DEAD_TRANSACTION;
-module_param_named(debug_mask, binder_debug_mask, uint, S_IWUSR | S_IRUGO);
+module_param_named(debug_mask, binder_debug_mask, uint, 0644);
 
 static char *binder_devices_param = CONFIG_ANDROID_BINDER_DEVICES;
 module_param_named(devices, binder_devices_param, charp, 0444);
@@ -160,7 +160,7 @@ static int binder_set_stop_on_user_error(const char *val,
return ret;
 }
 module_param_call(stop_on_user_error, binder_set_stop_on_user_error,
-   param_get_int, _stop_on_user_error, S_IWUSR | S_IRUGO);
+   param_get_int, _stop_on_user_error, 0644);
 
 #define binder_debug(mask, x...) \
do { \
@@ -4679,7 +4679,7 @@ static int binder_open(struct inode *nodp, struct file 
*filp)
 * anyway print all contexts that a given PID has, so this
 * is not a problem.
 */
-   proc->debugfs_entry = debugfs_create_file(strbuf, S_IRUGO,
+   proc->debugfs_entry = debugfs_create_file(strbuf, 0444,
binder_debugfs_dir_entry_proc,
(void *)(unsigned long)proc->pid,
_proc_fops);
@@ -5518,27 +5518,27 @@ static int __init binder_init(void)
 
if (binder_debugfs_dir_entry_root) {
debugfs_create_file("state",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
NULL,
_state_fops);
debugfs_create_file("stats",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
NULL,
_stats_fops);
debugfs_create_file("transactions",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
NULL,
_transactions_fops);
debugfs_create_file("transaction_log",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
_transaction_log,
_transaction_log_fops);
debugfs_create_file("failed_transaction_log",
-   S_IRUGO,
+   0444,
binder_debugfs_dir_entry_root,
_transaction_log_failed,
_transaction_log_fops);
-- 
2.15.0.631.g7ddcec0

[PATCH 1/1] drivers: android: Cleanup warnings

[Harsh Shandilya]

Ran checkpatch across the entire drivers/android
directory and fixed all relevant warnings. Summary
of changes done:

 -> Convert all symbolic permissions into their
octal equivalents.
 -> Use "%s", __func__ in logging macros where the
function name was previously hard-coded.
 -> Add a blank line to separate declarations from
statements according to the kernel coding style
guidelines.
 -> Fix linelength issues wherever possible.
 -> Fix-up a commented out statement to use // in place
of /* */ to silence checkpatch.

Most line-length warnings were ignored in favor
of code readability.

Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Cc: Todd Kjos <tk...@android.com>
Cc: Martijn Coenen <m...@android.com>
Cc: de...@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Harsh Shandilya <msfjar...@gmail.com>
---
 drivers/android/binder.c   | 39 ++-
 drivers/android/binder_alloc.c |  1 +
 2 files changed, 23 insertions(+), 17 deletions(-)

diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index bccec9de0533..2c06a42a6d9a 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -141,7 +141,7 @@ enum {
 };
 static uint32_t binder_debug_mask = BINDER_DEBUG_USER_ERROR |
BINDER_DEBUG_FAILED_TRANSACTION | BINDER_DEBUG_DEAD_TRANSACTION;
-module_param_named(debug_mask, binder_debug_mask, uint, S_IWUSR | S_IRUGO);
+module_param_named(debug_mask, binder_debug_mask, uint, 0644);
 
 static char *binder_devices_param = CONFIG_ANDROID_BINDER_DEVICES;
 module_param_named(devices, binder_devices_param, charp, 0444);
@@ -160,7 +160,7 @@ static int binder_set_stop_on_user_error(const char *val,
return ret;
 }
 module_param_call(stop_on_user_error, binder_set_stop_on_user_error,
-   param_get_int, _stop_on_user_error, S_IWUSR | S_IRUGO);
+   param_get_int, _stop_on_user_error, 0644);
 
 #define binder_debug(mask, x...) \
do { \
@@ -3250,6 +3250,7 @@ static int binder_thread_write(struct binder_proc *proc,
ret = -1;
if (increment && !target) {
struct binder_node *ctx_mgr_node;
+
mutex_lock(>context_mgr_node_lock);
ctx_mgr_node = context->binder_context_mgr_node;
if (ctx_mgr_node)
@@ -3356,7 +3357,8 @@ static int binder_thread_write(struct binder_proc *proc,
binder_debug(BINDER_DEBUG_USER_REFS,
 "%d:%d %s node %d ls %d lw %d tr %d\n",
 proc->pid, thread->pid,
-cmd == BC_INCREFS_DONE ? "BC_INCREFS_DONE" 
: "BC_ACQUIRE_DONE",
+cmd == BC_INCREFS_DONE ? "BC_INCREFS_DONE" 
:
+"BC_ACQUIRE_DONE",
 node->debug_id, node->local_strong_refs,
 node->local_weak_refs, node->tmp_refs);
binder_node_inner_unlock(node);
@@ -3394,7 +3396,8 @@ static int binder_thread_write(struct binder_proc *proc,
 "%d:%d BC_FREE_BUFFER u%016llx found 
buffer %d for %s transaction\n",
 proc->pid, thread->pid, (u64)data_ptr,
 buffer->debug_id,
-buffer->transaction ? "active" : 
"finished");
+buffer->transaction ? "active" :
+"finished");
 
if (buffer->transaction) {
buffer->transaction->buffer = NULL;
@@ -3858,7 +3861,8 @@ static int binder_thread_read(struct binder_proc *proc,
binder_stats_deleted(BINDER_STAT_TRANSACTION_COMPLETE);
} break;
case BINDER_WORK_NODE: {
-   struct binder_node *node = container_of(w, struct 
binder_node, work);
+   struct binder_node *node =
+   container_of(w, struct binder_node, work);
int strong, weak;
binder_uintptr_t node_ptr = node->ptr;
binder_uintptr_t node_cookie = node->cookie;
@@ -4467,8 +4471,8 @@ static long binder_ioctl(struct file *filp, unsigned int 
cmd, unsigned long arg)
unsigned int size = _IOC_SIZE(cmd);
void __user *ubuf = (void __user *)arg;
 
-   /*pr_info("binder_ioctl: %d:%d %x %lx\n",
-   proc->pid, current->pid, cmd, arg);*/
+   // pr_info("%s: %d:%d %x %lx\n",
+

[PATCH 1/1] drivers: android: Cleanup warnings

[Harsh Shandilya]

Ran checkpatch across the entire drivers/android
directory and fixed all relevant warnings. Summary
of changes done:

 -> Convert all symbolic permissions into their
octal equivalents.
 -> Use "%s", __func__ in logging macros where the
function name was previously hard-coded.
 -> Add a blank line to separate declarations from
statements according to the kernel coding style
guidelines.
 -> Fix linelength issues wherever possible.
 -> Fix-up a commented out statement to use // in place
of /* */ to silence checkpatch.

Most line-length warnings were ignored in favor
of code readability.

Cc: Greg Kroah-Hartman 
Cc: Todd Kjos 
Cc: Martijn Coenen 
Cc: de...@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Harsh Shandilya 
---
 drivers/android/binder.c   | 39 ++-
 drivers/android/binder_alloc.c |  1 +
 2 files changed, 23 insertions(+), 17 deletions(-)

diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index bccec9de0533..2c06a42a6d9a 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -141,7 +141,7 @@ enum {
 };
 static uint32_t binder_debug_mask = BINDER_DEBUG_USER_ERROR |
BINDER_DEBUG_FAILED_TRANSACTION | BINDER_DEBUG_DEAD_TRANSACTION;
-module_param_named(debug_mask, binder_debug_mask, uint, S_IWUSR | S_IRUGO);
+module_param_named(debug_mask, binder_debug_mask, uint, 0644);
 
 static char *binder_devices_param = CONFIG_ANDROID_BINDER_DEVICES;
 module_param_named(devices, binder_devices_param, charp, 0444);
@@ -160,7 +160,7 @@ static int binder_set_stop_on_user_error(const char *val,
return ret;
 }
 module_param_call(stop_on_user_error, binder_set_stop_on_user_error,
-   param_get_int, _stop_on_user_error, S_IWUSR | S_IRUGO);
+   param_get_int, _stop_on_user_error, 0644);
 
 #define binder_debug(mask, x...) \
do { \
@@ -3250,6 +3250,7 @@ static int binder_thread_write(struct binder_proc *proc,
ret = -1;
if (increment && !target) {
struct binder_node *ctx_mgr_node;
+
mutex_lock(>context_mgr_node_lock);
ctx_mgr_node = context->binder_context_mgr_node;
if (ctx_mgr_node)
@@ -3356,7 +3357,8 @@ static int binder_thread_write(struct binder_proc *proc,
binder_debug(BINDER_DEBUG_USER_REFS,
 "%d:%d %s node %d ls %d lw %d tr %d\n",
 proc->pid, thread->pid,
-cmd == BC_INCREFS_DONE ? "BC_INCREFS_DONE" 
: "BC_ACQUIRE_DONE",
+cmd == BC_INCREFS_DONE ? "BC_INCREFS_DONE" 
:
+"BC_ACQUIRE_DONE",
 node->debug_id, node->local_strong_refs,
 node->local_weak_refs, node->tmp_refs);
binder_node_inner_unlock(node);
@@ -3394,7 +3396,8 @@ static int binder_thread_write(struct binder_proc *proc,
 "%d:%d BC_FREE_BUFFER u%016llx found 
buffer %d for %s transaction\n",
 proc->pid, thread->pid, (u64)data_ptr,
 buffer->debug_id,
-buffer->transaction ? "active" : 
"finished");
+buffer->transaction ? "active" :
+"finished");
 
if (buffer->transaction) {
buffer->transaction->buffer = NULL;
@@ -3858,7 +3861,8 @@ static int binder_thread_read(struct binder_proc *proc,
binder_stats_deleted(BINDER_STAT_TRANSACTION_COMPLETE);
} break;
case BINDER_WORK_NODE: {
-   struct binder_node *node = container_of(w, struct 
binder_node, work);
+   struct binder_node *node =
+   container_of(w, struct binder_node, work);
int strong, weak;
binder_uintptr_t node_ptr = node->ptr;
binder_uintptr_t node_cookie = node->cookie;
@@ -4467,8 +4471,8 @@ static long binder_ioctl(struct file *filp, unsigned int 
cmd, unsigned long arg)
unsigned int size = _IOC_SIZE(cmd);
void __user *ubuf = (void __user *)arg;
 
-   /*pr_info("binder_ioctl: %d:%d %x %lx\n",
-   proc->pid, current->pid, cmd, arg);*/
+   // pr_info("%s: %d:%d %x %lx\n",
+   //  __func__, proc->pid, current->pid, cmd, arg);
 
binder_selftest_alloc(>a