From: Thomas Gleixner <tglx@linutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/5] gpio: langwell: Cleanup the interrupt mess
Date: Thu, 17 Mar 2011 22:38:38 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1103172236530.2787@localhost6.localdomain6> (raw)
In-Reply-To: <20110317195112.GE12824@angua.secretlab.ca>
On Thu, 17 Mar 2011, Grant Likely wrote:
> On Thu, Mar 17, 2011 at 07:32:43PM -0000, Thomas Gleixner wrote:
> > The langwell interrupt handler is interesting and breaks when an
> > architecture enables GENERIC_HARDIRQS_NO_DEPRECATED.
> >
> > Also this driver along with the other intel ones should depend on x86.
> >
> > The series cleans that up. The last patch 5/5 is RFC and needs a
> > close look and testing by folks at Intel.
>
> Applied first 4, thanks. Will apply last one when I get acks from the
> Intel folks.
Fair enough.
You should also poke those folks why they did write another driver for
the same gpio IP block. Though I wouldn't be surprised if we have more
than one copy of this in the tree. :(
Thanks,
tglx
prev parent reply other threads:[~2011-03-17 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 19:32 Thomas Gleixner
2011-03-17 19:32 ` [patch 1/5] gpio; Make Intel chipset gpio drivers depend on x86 Thomas Gleixner
2011-03-17 19:32 ` [patch 2/5] gpio-langwell-fix-crap.patch Thomas Gleixner
2011-03-17 19:32 ` [patch 3/5] gpio: langwell: Convert irq name space Thomas Gleixner
2011-03-17 19:32 ` [patch 4/5] gpio: langwell: Simplify demux loop Thomas Gleixner
2011-03-17 19:32 ` [patch 5/5] [RFC] gpio: langwell: Clear edge bit before handling Thomas Gleixner
2011-03-18 2:33 ` Du, Alek
2011-03-18 5:06 ` Grant Likely
2011-03-17 19:51 ` [patch 0/5] gpio: langwell: Cleanup the interrupt mess Grant Likely
2011-03-17 21:38 ` Thomas Gleixner [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=alpine.LFD.2.00.1103172236530.2787@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®