From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: intc: fix build error in interrupts.h
Date: Wed, 30 Mar 2011 04:51:28 +0000 [thread overview]
Message-ID: <20110330045124.GA19997@verge.net.au> (raw)
In-Reply-To: <4D928B6A.0@renesas.com>
On Wed, Mar 30, 2011 at 10:47:49AM +0900, Paul Mundt wrote:
> On Wed, Mar 30, 2011 at 10:46:18AM +0900, Yoshihiro Shimoda wrote:
> > Fix the problem that name of some functions changed.
> >
> > Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>
> Thomas already caught this, so it should be resolved soon.
FWIW, thanks for pointing me towards this patch.
It fixed a build problem I was seeing when building 2.6.39-rc1
for mackerel.
Drive-by Tested-by: Simon Horman <horms@verge.net.au>
prev parent reply other threads:[~2011-03-30 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 1:46 [PATCH] sh: intc: fix build error in interrupts.h Yoshihiro Shimoda
2011-03-30 1:47 ` Paul Mundt
2011-03-30 3:39 ` Yoshihiro Shimoda
2011-03-30 4:51 ` Simon Horman [this message]
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=20110330045124.GA19997@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@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).