From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] spi/pl022: Activate resourses before deactivate them in suspend
Date: Sun, 14 Oct 2012 14:27:07 +0900 [thread overview]
Message-ID: <20121014052705.GA22172@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAPDyKFpa8XoEy-kq3nq0dbRtM=a1wJ7cx=OzCOqMY1PmXrXJYw@mail.gmail.com>
On Fri, Oct 12, 2012 at 04:42:53PM +0200, Ulf Hansson wrote:
> Hi Mark,
>
> Just a kind remember on this. Do you see any problem merging this?
>
> Kind regards
> Ulf Hansson
>
> On 5 October 2012 09:43, Ulf Hansson <ulf.hansson@stericsson.com> wrote:
Don't top post and don't send contentless nags less than a week after
your original mail, especially not in the merge window when only urgent
bug fixes should be applied.
next prev parent reply other threads:[~2012-10-14 5:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 7:43 [PATCH] spi/pl022: Activate resourses before deactivate them in suspend Ulf Hansson
2012-10-12 14:42 ` Ulf Hansson
2012-10-14 5:27 ` Mark Brown [this message]
2012-10-27 21:46 ` Mark Brown
2012-10-28 19:52 ` Linus Walleij
2012-10-28 20:28 ` Ulf Hansson
2012-10-28 21:09 ` Alan Stern
2012-10-30 17:05 ` Ulf Hansson
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=20121014052705.GA22172@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).