linux-kernel - Re: [PATCH 00/03] gpio: R-Car and EM GPIO update

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] [day] [month] [year] [list]

Message-ID: <CACRpkdYZ07wrGiHtFww4TExUM8Ny13OtQZBQ3XqLc-hUC+-5+A@mail.gmail.com>
Date:	Tue, 19 Nov 2013 09:26:47 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Magnus Damm <magnus.damm@...il.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Simon Horman <horms@...ge.net.au>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH 00/03] gpio: R-Car and EM GPIO update

On Wed, Nov 13, 2013 at 11:59 PM, Magnus Damm <magnus.damm@...il.com> wrote:

> gpio: R-Car and EM GPIO update
>
> [PATCH 01/03] gpio: rcar: Use lazy disable and mask on suspend
> [PATCH 02/03] gpio: em: Setup gpiochip->dev
> [PATCH 03/03] gpio: em: Use lazy disable and mask on suspend
>
> Update the R-Car GPIO driver and the GPIO driver used on EMEV2 to use lazy
> disable and mask on suspend. This fixes the Suspend-to-RAM behavior to make
> sure wakeup sources are left enabled while suspending. Also include a small
> fix for gpio-em that fixes the DT use case.
>
> Signed-off-by: Magnus Damm <damm@...nsource.se>

These look OK but I see you and Laurent are discussing
patch 1, so whenever you feel ready with the series, please
resend so I can apply it.

Yours,
Linus Walleij
--
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/