From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: Amit Kucheria <amit.kucheria@verdurent.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"me@felipebalbi.com" <me@felipebalbi.com>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: usb_nop_xceiv_register() missing when OTG built as modules
Date: Wed, 26 May 2010 09:03:21 +0300 [thread overview]
Message-ID: <20100526060321.GE3069@nokia.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E7394044E61643A@dbde02.ent.ti.com>
On Mon, May 24, 2010 at 09:07:37AM +0200, ext Gupta, Ajay Kumar wrote:
>Hi,
>> Here is a compile-tested patch since I haven't seen this fixed in mainline
>> yet. It applies to the tip of Linus' tree.
>>
>> Attempting to remove usb_nop_xceiv_register() completely will require
>> someone
>> with more knowledge of davinci and blackfin archs to comment on what
>> boards
>> need the platform_device defined.
>
>NAK..
>This is an incorrect fix as it duplicates the code snippet which
>is already present in nop file.
I don't believe you understood the purpose of the original patch:
The idea is that currently, it's impossible to build a board which uses
nop transceiver and have that be a module because when you'll have an
undefined function being used on a board file.
Removing the call to nop_xceiv_register() and using a
platform_device_register() is the way to go, since it's only 4 ~ 5 lines
of code anyway.
ps: you really think that adding more and more ifdefs is better than
Amit's patch ??
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-05-26 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 0:09 usb_nop_xceiv_register() missing when OTG built as modules Kevin Hilman
2010-03-04 4:29 ` Gupta, Ajay Kumar
2010-03-04 17:32 ` Kevin Hilman
2010-03-05 3:50 ` Gupta, Ajay Kumar
2010-03-05 9:04 ` Felipe Balbi
2010-03-05 17:59 ` Kevin Hilman
2010-03-05 19:54 ` me
2010-03-05 22:02 ` Kevin Hilman
2010-05-22 23:53 ` Amit Kucheria
2010-05-24 7:07 ` Gupta, Ajay Kumar
2010-05-26 6:03 ` Felipe Balbi [this message]
2010-05-26 6:20 ` Gupta, Ajay Kumar
2010-05-26 6:53 ` Gupta, Ajay Kumar
2010-05-26 6:02 ` Felipe Balbi
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=20100526060321.GE3069@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=ajay.gupta@ti.com \
--cc=amit.kucheria@verdurent.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=tony@atomide.com \
/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).