devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <patrickdepinguin+devicetree-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	"Hans J. Koch" <hjk-vqZO0P4V72/QD6PfKP4TzA@public.gmane.org>,
	Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>,
	John Williams
	<john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v5] uio/pdrv_genirq: Add OF support
Date: Wed, 25 May 2011 09:27:57 +0200	[thread overview]
Message-ID: <BANLkTinOe5nDB27JKPTNpNyEgKgM0qS=rA@mail.gmail.com> (raw)
In-Reply-To: <20110524162452.GA22936-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Hi,

On Tue, May 24, 2011 at 6:24 PM, Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> wrote:
>
>> There was some unanswered question by Thomas De Scham, though.
>
> The answers to his question can be found in the discussions around previous
> versions of the patch.
>

I agree. After reading the entire thread a second time, I found the
answer: current 'workaround' is to let users modify the generic
driver's match table, while the real fix is to add runtime adding of
compatible strings to platform devices.

However, the latter functionality is not yet present, right?

Thanks,
Thomas

> Regards,
>
>   Wolfram
>
> --
> Pengutronix e.K.                           | Wolfram Sang                |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
>

  parent reply	other threads:[~2011-05-25  7:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05  6:40 [PATCH v5] uio/pdrv_genirq: Add OF support Michal Simek
     [not found] ` <1304577644-4024-1-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-05-06  0:47   ` Hans J. Koch
2011-05-12 13:53     ` Thomas De Schampheleire
2011-05-12 13:56     ` Thomas De Schampheleire
2011-05-12 17:03   ` Wolfram Sang
2011-05-24 11:27 ` Michal Simek
2011-05-24 12:36   ` Greg KH
2011-05-24 15:02     ` Hans J. Koch
2011-05-24 15:14       ` Greg KH
     [not found]         ` <20110524151413.GA25076-l3A5Bk7waGM@public.gmane.org>
2011-05-24 22:04           ` Hans J. Koch
2011-05-24 22:13             ` Greg KH
2011-05-24 16:24       ` Wolfram Sang
     [not found]         ` <20110524162452.GA22936-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-05-25  7:27           ` Thomas De Schampheleire [this message]
     [not found]             ` <BANLkTinOe5nDB27JKPTNpNyEgKgM0qS=rA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-25  7:28               ` Arnd Bergmann

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='BANLkTinOe5nDB27JKPTNpNyEgKgM0qS=rA@mail.gmail.com' \
    --to=patrickdepinguin+devicetree-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=gregkh-l3A5Bk7waGM@public.gmane.org \
    --cc=hjk-vqZO0P4V72/QD6PfKP4TzA@public.gmane.org \
    --cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 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).