linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Haojian Zhuang <haojian.zhuang@marvell.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: MFD_WM831X should depend on GENERIC_HARDIRQS
Date: Wed, 10 Mar 2010 14:12:30 +0100	[thread overview]
Message-ID: <10f740e81003100512u6d3430cy339cc4f833dafbb5@mail.gmail.com> (raw)
In-Reply-To: <20100310120155.GO24422@rakim.wolfsonmicro.main>

On Wed, Mar 10, 2010 at 13:01, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Mar 09, 2010 at 08:13:56PM +0100, Geert Uytterhoeven wrote:
>
>> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
>> This patch still hasn't made it. In addition, 3 more drivers started
>> to show the same problems
>> on architectures that don't use genirq yet, so I updated it.
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> TBH I'm surprised there's architectures that haven't implemented genirq
> yet.

There still are: m68k, s390, and sparc32. Converting m68k is on my
(too long) list...

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2010-03-10 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 21:00 [PATCH] mfd: MFD_WM831X should depend on GENERIC_HARDIRQS Geert Uytterhoeven
2009-12-15 22:13 ` Mark Brown
2010-03-09 19:13   ` Geert Uytterhoeven
2010-03-10 12:01     ` Mark Brown
2010-03-10 13:12       ` Geert Uytterhoeven [this message]
2010-03-11  0:30     ` Samuel Ortiz

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=10f740e81003100512u6d3430cy339cc4f833dafbb5@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=haojian.zhuang@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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).