From: Linus Walleij <linus.walleij@linaro.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: at91-pio4: handle suspend to ram
Date: Fri, 7 Apr 2017 14:34:03 +0200 [thread overview]
Message-ID: <CACRpkdZ=7e71XR++RWY8j5Lqb_UF6oMZzibCRo=76b8YPvcPiw@mail.gmail.com> (raw)
In-Reply-To: <20170407104846.5ghrcqc2ws4dkqxt@piout.net>
On Fri, Apr 7, 2017 at 12:48 PM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 07/04/2017 at 12:16:22 +0200, Linus Walleij wrote:
>> On Thu, Apr 6, 2017 at 3:36 PM, Alexandre Belloni
>> <alexandre.belloni@free-electrons.com> wrote:
>>
>> > When suspending to RAM, the power to the core is cut and the register
>> > values are lost. Save and restore more registers than just IMR.
>> >
>> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>
>> Should this be tagged for stable?
>>
>
> No because that particular suspend to ram mode is not yet implemented
> upstream.
>
>> Waiting for input from the AT91 maintainers here.
>>
>
> Well, I've been an AT91 maintainer for 2 years now and I have done all
> the AT91 pull requests since 3.16. I hope this qualifies me here.
So much for trying to keep MAINTAINERS in my head :(
I wish there was gmail integration so I could annotate people
with roles...
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-04-07 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 13:36 [PATCH] pinctrl: at91-pio4: handle suspend to ram Alexandre Belloni
2017-04-07 10:16 ` Linus Walleij
2017-04-07 10:48 ` Alexandre Belloni
2017-04-07 12:34 ` Linus Walleij [this message]
2017-04-07 12:45 ` Ludovic Desroches
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='CACRpkdZ=7e71XR++RWY8j5Lqb_UF6oMZzibCRo=76b8YPvcPiw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
/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).