From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Feng Tang <feng.tang@intel.com>
Cc: platform-driver-x86@vger.kernel.org, alan@linux.intel.com,
tglx@linutronix.de, Alek Du <alek.du@intel.com>
Subject: Re: [PATCH] intel_pmic_gpio: modify EOI handling following change of kernel irq subsystem
Date: Thu, 30 Dec 2010 13:41:17 +0000 [thread overview]
Message-ID: <20101230134117.GA12686@srcf.ucam.org> (raw)
In-Reply-To: <1293701574-28378-1-git-send-email-feng.tang@intel.com>
On Thu, Dec 30, 2010 at 05:32:54PM +0800, Feng Tang wrote:
> Latest kernel has many changes in IRQ subsystem and its interfaces, like adding
> "irq_eoi" for struct irq_chip, this patch will make it support both the new
> and old interface.
There's no point in having compatibility stubs in the mainline kernel.
Just fix the driver up to match the new behaviour.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-12-30 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 9:32 [PATCH] intel_pmic_gpio: modify EOI handling following change of kernel irq subsystem Feng Tang
2010-12-30 13:41 ` Matthew Garrett [this message]
2010-12-31 1:48 ` Feng Tang
2011-01-07 22:27 ` Matthew Garrett
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=20101230134117.GA12686@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan@linux.intel.com \
--cc=alek.du@intel.com \
--cc=feng.tang@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
/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