devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Williams <john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	hjk-vqZO0P4V72/QD6PfKP4TzA@public.gmane.org
Subject: Re: [PATCH v3] uio/pdrv_genirq: Add OF support
Date: Tue, 19 Apr 2011 11:58:25 +1000	[thread overview]
Message-ID: <BANLkTimFnfgiQ5aMq_KwqHP8p92pjOJJwg@mail.gmail.com> (raw)
In-Reply-To: <20110418160658.GD23814-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

On Tue, Apr 19, 2011 at 2:06 AM, Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> wrote:
> Hi,
>
>> For example with "uio" compatible string:
>> static const struct of_device_id __devinitconst uio_of_genirq_match[] = {
>>       { .compatible = "uio", },
>>       { /* empty for now */ },
>> };
>
> Please use a proper example with "vendor,device".
> (And after that it won't be empty anymore)

My vote is, and always has been 'generic-uio' :)

Putting some random vendor/device string in there is just nuts. Do you
really want a kernel patch every time some one binds their device to
it?

Or, is there no expectation that anybody would attempt to merge such a
pointless patch to begin with?

As we discussed at ELC, putting a real vendor/device in there is also
broken because all instances in the system wil bind to the generic
uio, which is not necessarily what is desired.

I know the arguments against the 'generic-uio' tag, but come on, let's
look at the lesser of two evils here!  I call BS on this DTS purity.

John

  parent reply	other threads:[~2011-04-19  1:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  8:50 [PATCH v3] uio/pdrv_genirq: Add OF support Michal Simek
2011-04-18 10:35 ` Paul Mundt
     [not found]   ` <20110418103513.GA27864-M7jkjyW5wf5g9hUCZPvPmw@public.gmane.org>
2011-04-18 11:10     ` Michal Simek
     [not found] ` <1303116654-5042-1-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-04-18 16:06   ` Wolfram Sang
     [not found]     ` <20110418160658.GD23814-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-04-19  1:58       ` John Williams [this message]
2011-04-19  6:11         ` Grant Likely
2011-04-19  7:32           ` Arnd Bergmann
     [not found]             ` <201104190932.31777.arnd-r2nGTMty4D4@public.gmane.org>
2011-04-19  8:42               ` Michal Simek
2011-04-19 12:37           ` John Williams
2011-04-19 13:02             ` Arnd Bergmann
2011-04-19 14:49             ` Grant Likely
2011-04-19 15:07               ` Arnd Bergmann
     [not found]                 ` <201104191707.40456.arnd-r2nGTMty4D4@public.gmane.org>
2011-04-19 15:45                   ` Grant Likely
     [not found]         ` <BANLkTimFnfgiQ5aMq_KwqHP8p92pjOJJwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-21 12:08           ` Wolfram Sang
     [not found]             ` <20110421120855.GC2135-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-04-21 23:46               ` John Williams
2011-04-22  6:07                 ` Wolfram Sang
2011-04-19  8:16       ` Michal Simek
2011-04-19  6:08 ` Grant Likely
2011-04-19  8:15   ` Michal Simek
2011-04-19 22:00   ` Hans J. Koch
2011-04-19 23:09     ` Scott Wood
2011-04-27 11:05   ` Michal Simek

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=BANLkTimFnfgiQ5aMq_KwqHP8p92pjOJJwg@mail.gmail.com \
    --to=john.williams-g5w7nranp4bdpfhejli6iq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=hjk-vqZO0P4V72/QD6PfKP4TzA@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).