linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: "Hans J. Koch" <hjk@linutronix.de>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
	linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: [PATCH 2/2] uio: add an of_genirq driver
Date: Sun, 14 Jun 2009 19:14:06 +0200	[thread overview]
Message-ID: <20090614171406.GA1010@pengutronix.de> (raw)
In-Reply-To: <20090614122136.GD3639@local>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Hello Hans,

> > +	uioinfo->irq = irq_of_parse_and_map(op->node, 0);
> > +	if (!uioinfo->irq)
> > +		uioinfo->irq = UIO_IRQ_NONE;
> 
> Please don't do this. It's inconsistent if all other UIO drivers require
> people to use UIO_IRQ_NONE and you also allow zero. UIO_IRQ_NONE was
> introduced because 0 may be a legal interrupt number on some platforms.

Yes, well, the '0' vs. 'NO_IRQ' thing is still not fully sorted out AFAIK. But
you are possibly right here, as long as irq_of_parse_and_map does return
NO_IRQ, I should explicitly check for it, like this:

	if (uioinfo->irq == NO_IRQ)
		uioinfo->irq = UIO_IRQ_NONE;

> > +/* Match table for of_platform binding */
> > +static const struct of_device_id __devinitconst uio_of_genirq_match[] = {
> 
> checkpatch.pl complains about that. Please check.

Did that, it is a false positive. See here:

http://lkml.indiana.edu/hypermail/linux/kernel/0906.1/02780.html

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-14 17:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  0:04 [PATCH 0/2] add OF wrapper for uio-pdrv-genirq Wolfram Sang
2009-06-12  0:04 ` [PATCH 1/2] uio/pdrv_genirq: Refactor probe routine to expose a generic part Wolfram Sang
2009-06-14 12:15   ` Hans J. Koch
2009-06-12  0:04 ` [PATCH 2/2] uio: add an of_genirq driver Wolfram Sang
2009-06-14 12:21   ` Hans J. Koch
2009-06-14 17:14     ` Wolfram Sang [this message]
2009-06-14 18:33       ` Hans J. Koch
2009-06-14 19:05         ` Wolfram Sang
2009-06-14 19:23           ` Hans J. Koch
2009-06-14 19:36             ` Wolfgang Grandegger
2009-06-14 20:34               ` Hans J. Koch
2009-06-14 22:00                 ` Wolfram Sang
2009-06-14 23:01                   ` Hans J. Koch
2009-06-14 23:46                     ` Wolfram Sang
2009-06-14 23:50                       ` Hans J. Koch
2009-06-14 19:27           ` Greg KH
2009-06-14 21:46             ` Wolfram Sang
2009-06-14 23:12     ` Alan Cox
2009-06-14 23:45       ` Hans J. Koch
2009-06-15  8:44         ` Alan Cox
2009-06-15  9:45       ` Benjamin Herrenschmidt
2009-06-14 14:40   ` Grant Likely
2009-06-16  9:04     ` Wolfram Sang
2009-06-16 12:46       ` 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=20090614171406.GA1010@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@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).