linux-kernel - Re: [PATCH] gpio-sch: Allow for more than 8 lines in the resume well

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: <CACRpkdYfDRtcQ4z4PdinpNKmTHHS5+T2asSPgRGHvGK1qRL_XQ@mail.gmail.com>
Date:	Wed, 27 Mar 2013 09:20:57 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Darren Hart <dvhart@...ux.intel.com>,
	Seth Heasley <seth.heasley@...el.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	stable@...r.kernel.org, Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH] gpio-sch: Allow for more than 8 lines in the resume well

On Wed, Mar 6, 2013 at 10:49 PM, Darren Hart <dvhart@...ux.intel.com> wrote:

> The E6xx (TunnelCreek) CPUs have 9 GPIO lines in the resume well. Update
> the resume functions to allow for more than 8 GPIO lines, using the core
> functions as a template.
>
> Cc: <stable@...r.kernel.org> # 3.4.x
> Cc: <stable@...r.kernel.org> # 3.8.x
> Cc: Grant Likely <grant.likely@...retlab.ca>
> Cc: Linus Walleij <linus.walleij@...aro.org>
> Signed-off-by: Darren Hart <dvhart@...ux.intel.com>

I have applied this for next (v3.10)

I cannot for my life figure out what kind of *regression* you are
fixing so that it should go into fixes for the -rc:s or the two stable
branches indicated above.

I need a more verbose commit message with descriptions of
user-percieved problems on deployed systems that for that.

BTW: are you interested in adding yourself as mainatiner of
this driver in the MAINTAINERS file Darren?

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/