All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Stefan Roese <sr@denx.de>
Cc: hjk@linutronix.de,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	gregkh@suse.de, Linux Kernel list <linux-kernel@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org,
	John Williams <john.williams@petalogix.com>
Subject: Re: UIO / of_genirq driver
Date: Fri, 3 Dec 2010 16:50:31 +0100	[thread overview]
Message-ID: <20101203155031.GC5636@pengutronix.de> (raw)
In-Reply-To: <201012031643.31428.sr@denx.de>

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


> Is there any update on this in the meantime? Do you know of any plans to re-
> work/-push this patchset? Just checking...

I had another look recently; I wouldn't like to just copy/paste the
"new_id"-mechanism from PCI because the code would then exist three
times in the kernel (PCMCIA being the third user I am aware of). I
wondered if it was feasible to make the "new-id"-code generic and make
those subsystems just use it. I haven't started working on it, though.

Kind regards,

   Wolfram

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

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

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <w.sang@pengutronix.de>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@lists.ozlabs.org,
	John Williams <john.williams@petalogix.com>,
	gregkh@suse.de,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	hjk@linutronix.de,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: UIO / of_genirq driver
Date: Fri, 3 Dec 2010 16:50:31 +0100	[thread overview]
Message-ID: <20101203155031.GC5636@pengutronix.de> (raw)
In-Reply-To: <201012031643.31428.sr@denx.de>

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


> Is there any update on this in the meantime? Do you know of any plans to re-
> work/-push this patchset? Just checking...

I had another look recently; I wouldn't like to just copy/paste the
"new_id"-mechanism from PCI because the code would then exist three
times in the kernel (PCMCIA being the third user I am aware of). I
wondered if it was feasible to make the "new-id"-code generic and make
those subsystems just use it. I haven't started working on it, though.

Kind regards,

   Wolfram

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

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

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <w.sang@pengutronix.de>
To: Stefan Roese <sr@denx.de>
Cc: hjk@linutronix.de,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	gregkh@suse.de, Linux Kernel list <linux-kernel@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org,
	John Williams <john.williams@petalogix.com>
Subject: Re: UIO / of_genirq driver
Date: Fri, 3 Dec 2010 16:50:31 +0100	[thread overview]
Message-ID: <20101203155031.GC5636@pengutronix.de> (raw)
In-Reply-To: <201012031643.31428.sr@denx.de>


[-- Attachment #1.1: Type: text/plain, Size: 670 bytes --]


> Is there any update on this in the meantime? Do you know of any plans to re-
> work/-push this patchset? Just checking...

I had another look recently; I wouldn't like to just copy/paste the
"new_id"-mechanism from PCI because the code would then exist three
times in the kernel (PCMCIA being the third user I am aware of). I
wondered if it was feasible to make the "new-id"-code generic and make
those subsystems just use it. I haven't started working on it, though.

Kind regards,

   Wolfram

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

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2010-12-03 15:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  7:13 UIO / of_genirq driver John Williams
2010-01-28  7:13 ` John Williams
2010-01-28  7:13 ` John Williams
2010-01-28 10:45 ` Wolfram Sang
2010-01-28 10:45   ` Wolfram Sang
2010-12-03 15:43   ` Stefan Roese
2010-12-03 15:43     ` Stefan Roese
2010-12-03 15:50     ` Wolfram Sang [this message]
2010-12-03 15:50       ` Wolfram Sang
2010-12-03 15:50       ` Wolfram Sang

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=20101203155031.GC5636@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sr@denx.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 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.