From: Linus Walleij <linus.walleij@linaro.org>
To: Darren Hart <dvhart@linux.intel.com>,
Seth Heasley <seth.heasley@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH] gpio-sch: Allow for more than 8 lines in the resume well
Date: Wed, 27 Mar 2013 09:20:57 +0100 [thread overview]
Message-ID: <CACRpkdYfDRtcQ4z4PdinpNKmTHHS5+T2asSPgRGHvGK1qRL_XQ@mail.gmail.com> (raw)
In-Reply-To: <dabdda74b7aabe3edece1c5edb9aed1c24093695.1362606482.git.dvhart@linux.intel.com>
On Wed, Mar 6, 2013 at 10:49 PM, Darren Hart <dvhart@linux.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@vger.kernel.org> # 3.4.x
> Cc: <stable@vger.kernel.org> # 3.8.x
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Darren Hart <dvhart@linux.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
next prev parent reply other threads:[~2013-03-27 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 21:49 [PATCH] gpio-sch: Allow for more than 8 lines in the resume well Darren Hart
2013-03-27 8:20 ` Linus Walleij [this message]
2013-03-27 16:05 ` Darren Hart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACRpkdYfDRtcQ4z4PdinpNKmTHHS5+T2asSPgRGHvGK1qRL_XQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=dvhart@linux.intel.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).