linux-kernel - Re: [PATCH v2 8/8] platform: x86: intel_bxtwc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 24 Apr 2017 10:26:35 +0100
From:   Lee Jones <lee.jones@...aro.org>
To:     Darren Hart <dvhart@...radead.org>
Cc:     sathyanarayanan.kuppuswamy@...ux.intel.com, gnurou@...il.com,
        linus.walleij@...aro.org, edubezval@...il.com, rui.zhang@...el.com,
        andy@...radead.org, linux-gpio@...r.kernel.org,
        linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
        platform-driver-x86@...r.kernel.org, sathyaosid@...il.com
Subject: Re: [PATCH v2 8/8] platform: x86: intel_bxtwc_tmu: remove first
 level irq unmask

On Fri, 21 Apr 2017, Darren Hart wrote:

> On Fri, Apr 14, 2017 at 04:26:00PM -0700, sathyanarayanan.kuppuswamy@...ux.intel.com wrote:
> > From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>
> > 
> > Currently in WCOVE PMIC mfd driver, all second level irq chips
> 
> By currently I believe you mean after the earlier patch in this series is
> applied, correct? This one is dependent on the previous one?
> 
> > are chained to the respective first level irqs. So there is no
> > need for explicitly unmasking the first level irq in this
> > driver. This patches removes this level 1 irq unmask support.
> > 
> > Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>
> 
> For platform drivers x86:
> 
> Reviewed-by: Darren Hart (VMware) <dvhart@...radead.org>
> 
> Are you working with a specific maintainers to pull this in as a series? With so
> many subsystems, we need to coordinate to make sure we don't make a mess for
> Linus. Given the interdependencies, I'd recommend someone pull the series in as
> a whole - maybe into MFD? Lee, do you have a preference?

I am happy to take the set, however I think v4.12 is an unlikely
candidate, since there still have quite a few patches which are yet to
receive review and the merge-window opens in 6 days.

Once we have all the required Acks, I'll push the set into -next where
it can sit for a good soak test until v4.13.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog