From: Sean MacLennan <smaclennan-Qtffpm9i2AVWk0Htik3J/w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: [PATCH RESEND 3/3] i2c/ibm-iic: drop NO_IRQ
Date: Fri, 2 Apr 2010 15:47:18 -0400 [thread overview]
Message-ID: <20100402154718.4976f2d9@lappy.seanm.ca> (raw)
In-Reply-To: <1270167421-5205-4-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Fri, 2 Apr 2010 02:17:01 +0200
Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> wrote:
> Drop NO_IRQ as 0 is the preferred way to describe 'no irq'
> (http://lkml.org/lkml/2005/11/21/221). This change is safe, as the
> driver is only used on powerpc, where NO_IRQ is 0 anyhow.
>
> Signed-off-by: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> Acked-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Acked-by: Sean MacLennan <smaclennan-Qtffpm9i2AVWk0Htik3J/w@public.gmane.org>
Cheers,
Sean
WARNING: multiple messages have this Message-ID (diff)
From: Sean MacLennan <smaclennan@pikatech.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH RESEND 3/3] i2c/ibm-iic: drop NO_IRQ
Date: Fri, 2 Apr 2010 15:47:18 -0400 [thread overview]
Message-ID: <20100402154718.4976f2d9@lappy.seanm.ca> (raw)
In-Reply-To: <1270167421-5205-4-git-send-email-w.sang@pengutronix.de>
On Fri, 2 Apr 2010 02:17:01 +0200
Wolfram Sang <w.sang@pengutronix.de> wrote:
> Drop NO_IRQ as 0 is the preferred way to describe 'no irq'
> (http://lkml.org/lkml/2005/11/21/221). This change is safe, as the
> driver is only used on powerpc, where NO_IRQ is 0 anyhow.
>
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
Acked-by: Sean MacLennan <smaclennan@pikatech.com>
Cheers,
Sean
next prev parent reply other threads:[~2010-04-02 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 0:16 Delete NO_IRQ usage from I2C subsystem Wolfram Sang
2010-04-02 0:16 ` Wolfram Sang
[not found] ` <1270167421-5205-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-04-02 0:16 ` [PATCH RESEND 1/3] i2c/mpc: drop NO_IRQ Wolfram Sang
2010-04-02 0:16 ` Wolfram Sang
2010-04-02 0:17 ` [PATCH RESEND 2/3] i2c/cpm: " Wolfram Sang
2010-04-02 0:17 ` Wolfram Sang
[not found] ` <1270167421-5205-3-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-04-02 11:34 ` Jochen Friedrich
2010-04-02 11:34 ` Jochen Friedrich
2010-04-02 0:17 ` [PATCH RESEND 3/3] i2c/ibm-iic: " Wolfram Sang
2010-04-02 0:17 ` Wolfram Sang
[not found] ` <1270167421-5205-4-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-04-02 19:47 ` Sean MacLennan [this message]
2010-04-02 19:47 ` Sean MacLennan
2010-04-27 7:06 ` Benjamin Herrenschmidt
2010-04-27 7:12 ` Wolfram Sang
2010-04-27 7:12 ` Wolfram Sang
2010-04-27 7:45 ` Benjamin Herrenschmidt
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=20100402154718.4976f2d9@lappy.seanm.ca \
--to=smaclennan-qtffpm9i2avwk0htik3j/w@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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.