From: Tony Lindgren <tony@atomide.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3.4-rc4] ARM: OMAP1: Amstrad Delta: Fix wrong IRQ base in FIQ handler
Date: Mon, 7 May 2012 15:10:07 -0700 [thread overview]
Message-ID: <20120507221007.GN5088@atomide.com> (raw)
In-Reply-To: <1470735.vzc89Ry7Ka@acer>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120507 14:21]:
> Dnia piątek, 4 maja 2012 09:59:49 Tony Lindgren pisze:
> > * Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120430 10:30]:
> > > Commit 384ebe1c2849160d040df3e68634ec506f13d9ff, "gpio/omap: Add DT
> > > support to GPIO driver", introduced dynamic IRQ numbering of OMAP
> GPIO
> > > interrupts, breaking all IH_GPIO_BASE based IRQ number calculations.
> > > This issue was corrected in the OMAP GPIO driver and the related
> header
> > > file with commit 25db711df3258d125dc1209800317e5c0ef3c870,
> "gpio/omap:
> > > Fix IRQ handling for SPARSE_IRQ".
> > >
> > > However, the Amstrad Delta FIQ handler, which replaces the gpio-omap
> > > driver in serving GPIO interrupts on this board, still uses that
> > > outdated method. Fix it.
> >
> > Thanks applying into fixes.
>
> Hi Tony,
> Thanks for taking this patch, but I ca't see it applied into your fixes
> branch (the last one sitting there is "Linux 3.4-rc4" by Linus). Am I
> missing something?
Oops, sorry forgot to push it out. Pushed out now, so it should appear
on the mirrors shortly.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3.4-rc4] ARM: OMAP1: Amstrad Delta: Fix wrong IRQ base in FIQ handler
Date: Mon, 7 May 2012 15:10:07 -0700 [thread overview]
Message-ID: <20120507221007.GN5088@atomide.com> (raw)
In-Reply-To: <1470735.vzc89Ry7Ka@acer>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120507 14:21]:
> Dnia pi?tek, 4 maja 2012 09:59:49 Tony Lindgren pisze:
> > * Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120430 10:30]:
> > > Commit 384ebe1c2849160d040df3e68634ec506f13d9ff, "gpio/omap: Add DT
> > > support to GPIO driver", introduced dynamic IRQ numbering of OMAP
> GPIO
> > > interrupts, breaking all IH_GPIO_BASE based IRQ number calculations.
> > > This issue was corrected in the OMAP GPIO driver and the related
> header
> > > file with commit 25db711df3258d125dc1209800317e5c0ef3c870,
> "gpio/omap:
> > > Fix IRQ handling for SPARSE_IRQ".
> > >
> > > However, the Amstrad Delta FIQ handler, which replaces the gpio-omap
> > > driver in serving GPIO interrupts on this board, still uses that
> > > outdated method. Fix it.
> >
> > Thanks applying into fixes.
>
> Hi Tony,
> Thanks for taking this patch, but I ca't see it applied into your fixes
> branch (the last one sitting there is "Linux 3.4-rc4" by Linus). Am I
> missing something?
Oops, sorry forgot to push it out. Pushed out now, so it should appear
on the mirrors shortly.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3.4-rc4] ARM: OMAP1: Amstrad Delta: Fix wrong IRQ base in FIQ handler
Date: Mon, 7 May 2012 15:10:07 -0700 [thread overview]
Message-ID: <20120507221007.GN5088@atomide.com> (raw)
In-Reply-To: <1470735.vzc89Ry7Ka@acer>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120507 14:21]:
> Dnia piątek, 4 maja 2012 09:59:49 Tony Lindgren pisze:
> > * Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120430 10:30]:
> > > Commit 384ebe1c2849160d040df3e68634ec506f13d9ff, "gpio/omap: Add DT
> > > support to GPIO driver", introduced dynamic IRQ numbering of OMAP
> GPIO
> > > interrupts, breaking all IH_GPIO_BASE based IRQ number calculations.
> > > This issue was corrected in the OMAP GPIO driver and the related
> header
> > > file with commit 25db711df3258d125dc1209800317e5c0ef3c870,
> "gpio/omap:
> > > Fix IRQ handling for SPARSE_IRQ".
> > >
> > > However, the Amstrad Delta FIQ handler, which replaces the gpio-omap
> > > driver in serving GPIO interrupts on this board, still uses that
> > > outdated method. Fix it.
> >
> > Thanks applying into fixes.
>
> Hi Tony,
> Thanks for taking this patch, but I ca't see it applied into your fixes
> branch (the last one sitting there is "Linux 3.4-rc4" by Linus). Am I
> missing something?
Oops, sorry forgot to push it out. Pushed out now, so it should appear
on the mirrors shortly.
Tony
next prev parent reply other threads:[~2012-05-07 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:26 [PATCH 3.4-rc4] ARM: OMAP1: Amstrad Delta: Fix wrong IRQ base in FIQ handler Janusz Krzysztofik
2012-04-30 17:26 ` Janusz Krzysztofik
2012-05-04 16:59 ` Tony Lindgren
2012-05-04 16:59 ` Tony Lindgren
2012-05-07 21:16 ` Janusz Krzysztofik
2012-05-07 21:16 ` Janusz Krzysztofik
2012-05-07 22:10 ` Tony Lindgren [this message]
2012-05-07 22:10 ` Tony Lindgren
2012-05-07 22:10 ` Tony Lindgren
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=20120507221007.GN5088@atomide.com \
--to=tony@atomide.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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.