From: Sedat Dilek <sedat.dilek@gmail.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Dmitry Kasatkin <d.kasatkin@samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 28 [ xhci build breakage ]
Date: Thu, 29 Aug 2013 10:02:13 +0200 [thread overview]
Message-ID: <CA+icZUWNVCtRn_aK0ndXxmqutM4Sc_PJN4ei0m5phu6-CwO_+g@mail.gmail.com> (raw)
In-Reply-To: <20130828211546.GH26483@xanatos>
On Wed, Aug 28, 2013 at 11:15 PM, Sarah Sharp
<sarah.a.sharp@linux.intel.com> wrote:
> On Wed, Aug 28, 2013 at 07:39:14PM +0200, Sedat Dilek wrote:
>> On Wed, Aug 28, 2013 at 7:24 PM, Dmitry Kasatkin <d.kasatkin@samsung.com> wrote:
>> Still noone answered me why "drivers/usb/host/xhci-ring.c" does NOT
>> include <linux/device.h> (dev_info_ratelimited() and other defines).
>> I am expecting that... even I see...
>>
>> drivers/usb/host/.xhci-ring.o.cmd:715: include/linux/device.h \
>>
>> ...where I don't know why this happens.
>>
>> ( For me this is a bit more important than """trimming""" my
>> responses, I keep the history... )
>>
>> - Sedat -
>>
>> P.S.: List of includes in xhci-ring.c
>>
>> $ grep ^'#include' -nr drivers/usb/host/xhci-ring.c
>> 67:#include <linux/scatterlist.h>
>> 68:#include <linux/slab.h>
>> 69:#include "xhci.h"
>> 70:#include "xhci-trace.h"
>
> Because a header that xhci-ring.c uses includes device.h instead.
>
> drivers/usb/host/xhci/xhci-ring.c includes
> drivers/usb/host/xhci.h which includes
> include/linux/usb.h which includes
> include/linux/device.h
>
> All USB host controllers depend on including usb.h, so I don't think
> there's a need for the driver to explicitly include device.h.
>
Thanks for the explanations.
On the one hand it is a fine thingie to place include-files at one
single place - think of renamed or moved (uapi) include-files.
Looking at xhci-ring.c means for me to dig through 3 or 4 files as
someone not dealing everyday with USB stuff.
What is the effect of CONFIG_DYNAMIC_DEBUG=[y|n] in the affected code?
- Sedat -
P.S.: The forgotten patch is now in usb-next, but I don't see any
credits, coins, gold, platin...
next prev parent reply other threads:[~2013-08-29 8:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 9:49 linux-next: Tree for Aug 28 [ xhci build breakage ] Sedat Dilek
2013-08-28 9:56 ` Sedat Dilek
2013-08-28 10:29 ` Sedat Dilek
[not found] ` <CA+icZUVTzMxS4f3kZnauDkrpf4vwMbS3zd7ECOhE37S_FF83UA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-28 10:38 ` Sedat Dilek
2013-08-28 10:43 ` Dmitry Kasatkin
2013-08-28 10:46 ` Sedat Dilek
2013-08-28 10:52 ` Sedat Dilek
2013-08-28 10:53 ` Dmitry Kasatkin
2013-08-28 10:58 ` Sedat Dilek
2013-08-28 11:19 ` Sedat Dilek
2013-08-28 15:17 ` Sedat Dilek
2013-08-28 16:59 ` Sarah Sharp
2013-08-28 17:18 ` Greg Kroah-Hartman
2013-08-28 17:37 ` Sarah Sharp
2013-08-28 17:24 ` Dmitry Kasatkin
2013-08-28 17:39 ` Sedat Dilek
2013-08-28 21:15 ` Sarah Sharp
2013-08-29 8:02 ` Sedat Dilek [this message]
2013-08-29 16:54 ` Sarah Sharp
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=CA+icZUWNVCtRn_aK0ndXxmqutM4Sc_PJN4ei0m5phu6-CwO_+g@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=d.kasatkin@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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).