[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C35945F.9050502@ru.mvista.com>
Date: Thu, 08 Jul 2010 13:03:27 +0400
From: Sergei Shtylyov <sshtylyov@...sta.com>
To: Greg KH <gregkh@...e.de>
CC: Patrick Pannuto <ppannuto@...eaurora.org>,
dbrownell@...rs.sourceforge.net, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, sboyd@...eaurora.org
Subject: Re: [PATCH] usb: gadget: #include device.h in gadget.h
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.
>> 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?
struct usb_gadget {
/* readonly to gadget driver */
const struct usb_gadget_ops *ops;
struct usb_ep *ep0;
struct list_head ep_list; /* of usb_ep */
enum usb_device_speed speed;
unsigned is_dualspeed:1;
unsigned is_otg:1;
unsigned is_a_peripheral:1;
unsigned b_hnp_enable:1;
unsigned a_hnp_support:1;
unsigned a_alt_hnp_support:1;
const char *name;
struct device dev;
};
How this is going to work with "empty prototype"?.
> Generally, having header files include header files is frowned apon, and
> a number of people have been working on slowly unwinding a lot of this
> type of mess that we currently have.
IMO they could put their time to better use.
>> include/linux/usb/gadget.h: In function 'set_gadget_data':
>> include/linux/usb/gadget.h:492:
>> error: implicit declaration of function 'dev_set_drvdata'
> Ick, but then, this gets messier.
What gets messier?
> 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.
> thanks,
> greg k-h
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists