From: Wolfram Sang <w.sang@pengutronix.de>
To: linux-i2c@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: i2c/janitoral: drop NO_IRQ from the subsystem
Date: Thu, 22 Oct 2009 23:11:25 +0200 [thread overview]
Message-ID: <1256245888-25210-1-git-send-email-w.sang@pengutronix.de> (raw)
Hello,
after having to deal with NO_IRQ confusion more than once, I decided to start a
bit of janitorial work and remove it from the i2c-subsystem. Detail for better
using 0 as "no irq" can be found here: http://lkml.org/lkml/2005/11/21/221
Regards,
Wolfram
next reply other threads:[~2009-10-22 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 21:11 Wolfram Sang [this message]
2009-10-22 21:11 ` [PATCH 1/3] i2c/mpc: drop NO_IRQ Wolfram Sang
2009-10-22 21:11 ` [PATCH 2/3] i2c/cpm: " Wolfram Sang
2009-10-22 21:11 ` [PATCH 3/3] i2c/ibm-iic: " Wolfram Sang
2010-02-16 16:01 ` Grant Likely
2010-02-16 15:59 ` [PATCH 2/3] i2c/cpm: " Grant Likely
2010-02-16 15:59 ` [PATCH 1/3] i2c/mpc: " Grant Likely
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=1256245888-25210-1-git-send-email-w.sang@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).