From: James Cloos <cloos@jhcloos.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: found __[us]{8,16,32,64} type without #include <linux/types.h>
Date: Mon, 12 Sep 2011 11:27:03 -0400 [thread overview]
Message-ID: <m3zki9wzkw.fsf@jhcloos.com> (raw)
In-Reply-To: <201109091629.52879.arnd@arndb.de> (Arnd Bergmann's message of "Fri, 9 Sep 2011 16:29:52 +0200")
>>>>> "AB" == Arnd Bergmann <arnd@arndb.de> writes:
AB> The script only checks for direct inclusions of types.h, while the
AB> drm headers get it from drm.h.
I see. It had been quite some time since I last did a make 1>/dev/null,
long enough that I hadn't noticed that message before.
It is good to know that it is a false positive.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
prev parent reply other threads:[~2011-09-12 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:22 found __[us]{8,16,32,64} type without #include <linux/types.h> James Cloos
2011-09-09 14:29 ` Arnd Bergmann
2011-09-12 15:27 ` James Cloos [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=m3zki9wzkw.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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