From: Grant Likely <grant.likely@secretlab.ca>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
Peter Huewe <peterhuewe@gmx.de>
Subject: Re: [PATCH] spi: Fix builderror in spi-pl022.c
Date: Tue, 20 Sep 2011 15:52:02 -0600 [thread overview]
Message-ID: <20110920215202.GQ7781@ponder.secretlab.ca> (raw)
In-Reply-To: <CACRpkdbsUMCvBofKjExiB2wCbK9CwpcXr5xmShJ4SHEGAAH4Bw@mail.gmail.com>
On Tue, Sep 20, 2011 at 10:45:41PM +0200, Linus Walleij wrote:
> On Mon, Sep 5, 2011 at 2:45 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Sun, Aug 28, 2011 at 9:26 PM, Peter Huewe <peterhuewe@gmx.de> wrote:
> >
> >> This patch fixes a build error, introduced by commit (67fc8b9f, "PM: add
> >> runtime PM support to core Primecell driver") which unfortunately was a little
> >> bit incomplete and did contain a typo (11 instead of 22).
> >> I'm not sure how this patch could have been tested back then, if it
> >> doesn't even compile ;)
> >
> > Grant can you please apply this patch? Right now linux-next is
> > breaking because of this missing patch...
>
> Ping on this... ignore if it's been picked already.
It's not a patch that went through my tree, so I cannot pick it up.
g.
next prev parent reply other threads:[~2011-09-20 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Qvo1q-0000qv-TQ@rmk-PC.arm.linux.org.uk>
2011-08-28 19:26 ` Peter Huewe
2011-08-28 20:06 ` Russell King - ARM Linux
2011-08-29 8:41 ` Linus Walleij
2011-09-05 12:45 ` Linus Walleij
2011-09-20 20:45 ` Linus Walleij
2011-09-20 21:52 ` Grant Likely [this message]
2011-09-21 13:10 ` Russell King - ARM Linux
2011-09-21 15:54 ` Linus Walleij
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=20110920215202.GQ7781@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=peterhuewe@gmx.de \
--cc=rjw@sisk.pl \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=spi-devel-general@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®