From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Patrick Pannuto <ppannuto@codeaurora.org>
Cc: dbrownell@users.sourceforge.net, gregkh@suse.de,
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, 08 Jul 2010 23:12:41 +0400 [thread overview]
Message-ID: <4C362329.7070900@ru.mvista.com> (raw)
In-Reply-To: <4C35200C.2040209@codeaurora.org>
Hello.
Patrick Pannuto 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
Sigh, I've already submitted a more complete patch, adding 6 #include's
but it seems that prevailing opinion in this list is to leave things as they
are in the header, and deal with the fallout wherever it's used.
[...]
> diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
> index bbf45d5..ddca035 100644
> --- a/include/linux/usb/gadget.h
> +++ b/include/linux/usb/gadget.h
> @@ -15,6 +15,8 @@
> #ifndef __LINUX_USB_GADGET_H
> #define __LINUX_USB_GADGET_H
>
> +#include <linux/device.h>
> +
Besides, this is not against the recent kernel -- there should be #include
<linux/slab.h> here.
> struct usb_ep;
>
> /**
WBR, Sergei
prev parent reply other threads:[~2010-07-08 19:13 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
2010-07-08 17:46 ` Sergei Shtylyov
2010-07-08 19:12 ` Sergei Shtylyov [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=4C362329.7070900@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ppannuto@codeaurora.org \
--cc=sboyd@codeaurora.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