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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150403142922.GL24598@io.lakedaemon.net>
Date:	Fri, 3 Apr 2015 14:29:22 +0000
From:	Jason Cooper <jason@...edaemon.net>
To:	Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc:	Andrew Lunn <andrew@...n.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
	linux-arm-kernel@...ts.infradead.org,
	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Boris BREZILLON <boris.brezillon@...e-electrons.com>,
	Lior Amsalem <alior@...vell.com>,
	Tawfik Bayouk <tawfik@...vell.com>,
	Nadav Haklai <nadavh@...vell.com>
Subject: Re: [PATCH 4/5] irqchip: armada-370-xp: Allow using wakeup source

On Fri, Apr 03, 2015 at 09:17:55AM +0200, Gregory CLEMENT wrote:
> Hi Jason,
> 
> On 03/04/2015 01:23, Jason Cooper wrote:
> > On Mon, Mar 30, 2015 at 04:04:37PM +0200, Gregory CLEMENT wrote:
> >> On the Armada 370/XP SoCs, in standby mode the SoC stay powered and it
> >> is possible to wake-up from any interrupt sources. This patch adds
> >> flag to the MPIC irqchip driver to let linux know this.
> >>
> >> Signed-off-by: Gregory CLEMENT <gregory.clement@...e-electrons.com>
> >> ---
> >>  drivers/irqchip/irq-armada-370-xp.c | 1 +
> >>  1 file changed, 1 insertion(+)
> > 
> > Applied to irqchip/mvebu
> 
> Thanks!
> 
> Do you agree to take also the patch 3?

hmmm...

> It modifies a file in mach-mvebu (board-v7.c) but it depends on a patch
> located in irqchip: "irqchip: gic: Add an entry point to set up irqchip flags"

Yeah, I saw that.  Do you forsee any merge conflicts with mvebu?  The reason I
ask is that it looks like I'm going to be sending directly to Linus this
cycle.  I'd really prefer to hold off a cycle on that patch.  I'm not
100% certain my second PR (stacked domain/DT break) is going to get
accepted.  Which is what this patch depends on.

thoughts?

thx,

Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ