From: Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: of_match_table on non-DT builds
Date: Tue, 9 Nov 2010 08:07:55 -0800 [thread overview]
Message-ID: <20101109160755.GA7870@suse.de> (raw)
In-Reply-To: <AANLkTi=11Jok3eujFwvji8ON1urcdeebCkJZgNrF=em5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Nov 09, 2010 at 09:01:17AM -0700, Grant Likely wrote:
> On Tue, Nov 9, 2010 at 8:27 AM, Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Grant,
> >
> > With the of_match_table pointer only enabled with CONFIG_OF in struct
> > device_driver, all drivers will have to have #ifdefs around their
> > of_match_table if you want to build them for non-devicetree platforms. This
> > is just the tip of the iceberg as all probe related OF calls have to be
> > ifdef'ed. Is this the intention?
>
> Not really, and I'm not entirely sure about the best way to handle
> this. I might handle the of_match_table pointer using a macro so that
> the #ifdefs can be dropped in each individual device driver
> definition, or I might ask Greg to drop the #ifdefs around
> of_match_table in struct device_driver, but I don't really want to
> increase the size of struct device_driver for non-devicetree users.
That's ok, it's not that big of a deal to drop the #ifdef, especially if
it makes the .c files more "sane".
I'll work on merging the dma stuff in 'struct device' to a single
pointer, to get the space back, so you should be fine.
thanks,
greg k-h
prev parent reply other threads:[~2010-11-09 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 15:27 of_match_table on non-DT builds Rob Herring
[not found] ` <4CD9684E.7080606-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-11-09 16:01 ` Grant Likely
[not found] ` <AANLkTi=11Jok3eujFwvji8ON1urcdeebCkJZgNrF=em5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-09 16:07 ` Greg KH [this message]
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=20101109160755.GA7870@suse.de \
--to=gregkh-l3a5bk7wagm@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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 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.