All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: sh73a0: fixup RELOC_BASE of intca_irq_pins_desc
Date: Mon, 27 Aug 2012 08:30:33 +0000	[thread overview]
Message-ID: <20120827083031.GC29274@verge.net.au> (raw)
In-Reply-To: <87y5l95bfg.wl%kuninori.morimoto.gx@renesas.com>

On Mon, Aug 20, 2012 at 07:48:40PM -0700, Kuninori Morimoto wrote:
> 
> Hi Rafael
> 
> This patch is required for v3.6-rcX
> 
> > On Mon, Aug 20, 2012 at 05:35:52PM -0700, Kuninori Morimoto wrote:
> > > sh73a0 :: intca_irq_pins_desc irq table had conflict
> > > from irq 552 to irq 557 before.
> > > But the second controller was simply trampling the
> > > first one by way of the -EEXIST case from irq_alloc_desc_at().
> > > 
> > > But now, we have irqdomain support from
> > > 1d6a21b0a672fb29b01ccf397d478e0541e17716
> > > (sh: intc: initial irqdomain support)
> > > 
> > > The irqdomain code has simply tightened down the sanity checks and
> > > error path. So, sh73a0 CPU board got some WARNING when booting now.
> > > This patch fixup RELOC_BASE to solve this issue.
> > > 
> > > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > > ---
> > > This patch is for paul/sh-latest branch
> > > 
> > This can go through Rafael's tree, as nothing here depends on anything I
> > have outstanding. I have the multi-evt fix pending, but that's about it.
> 
> Best regards

For the record, Rafael sent a pull request "Renesas ARM-based SoC fix for
v3.6" which includes this patch.

  parent reply	other threads:[~2012-08-27  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  0:35 [PATCH] ARM: shmobile: sh73a0: fixup RELOC_BASE of intca_irq_pins_desc Kuninori Morimoto
2012-08-21  0:54 ` Paul Mundt
2012-08-21  2:48 ` Kuninori Morimoto
2012-08-27  8:30 ` Simon Horman [this message]
2012-08-31  6:55 ` Tetsuyuki Kobayashi
2012-08-31  7:16 ` Simon Horman

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=20120827083031.GC29274@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.