From: Greg KH <gregkh@suse.de>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: Patrick Pannuto <ppannuto@codeaurora.org>,
dbrownell@users.sourceforge.net, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, sboyd@codeaurora.org
Subject: Re: [PATCH] usb: gadget: #include device.h in gadget.h
Date: Thu, 8 Jul 2010 08:13:45 -0700 [thread overview]
Message-ID: <20100708151345.GB12452@suse.de> (raw)
In-Reply-To: <4C35945F.9050502@ru.mvista.com>
On Thu, Jul 08, 2010 at 01:03:27PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> Greg KH wrote:
>
> >>gadget.h uses structures defined in device.h, it must include it. In
> >>most cases, gadget.h is preceded by linux/platform_device.h, but if
> >>you are grouping headers sanely, device.h may not be pulled in until
> >>*after* gadget (e.g. mach/msm_device.h), thus gadget.h should not
> >>rely on something else #including device.h
>
> As well as a number of other headers. I have postaed a patch
> addressing the missing #include's already.
Yes I know, and my same statment stands.
> >>include/linux/usb/gadget.h:488: error: field 'dev' has incomplete type
>
> >Why not just provide an "empty" prototype for whatever is needed.
>
> Empty prototype of what, 'struct device'? Have you looked at the code at all?
Nope, I try not to :)
> struct device dev;
Ok, that wouldn't work.
> >How about just fixing up the .c file that the problem happens in, to
> >include device.h first? Is this an issue in the current tree somehow?
>
> In my opinion, this is just insane approach.
Sorry, but that seems to go against what the rest of the kernel is
doing.
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-08 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 0:47 [PATCH] usb: gadget: #include device.h in gadget.h Patrick Pannuto
2010-07-08 3:34 ` Greg KH
2010-07-08 9:03 ` Sergei Shtylyov
2010-07-08 15:13 ` Greg KH [this message]
2010-07-08 17:46 ` Sergei Shtylyov
2010-07-08 19:12 ` Sergei Shtylyov
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=20100708151345.GB12452@suse.de \
--to=gregkh@suse.de \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ppannuto@codeaurora.org \
--cc=sboyd@codeaurora.org \
--cc=sshtylyov@mvista.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