mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Julien Cristau <jcristau@debian.org>
Cc: Alexander Shishkin <virtuoso@slind.org>,
	linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: fix headers to include linux/types.h
Date: Wed, 1 Dec 2010 11:38:41 -0800	[thread overview]
Message-ID: <20101201113841.46e92def.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101201165418.GU5063@radis.liafa.jussieu.fr>

On Wed, 1 Dec 2010 17:54:18 +0100
Julien Cristau <jcristau@debian.org> wrote:

> On Wed, Dec  1, 2010 at 17:10:42 +0200, Alexander Shishkin wrote:
> 
> > For headers that get exported to userland and make use of u32 style
> > type names, it is advised to include linux/types.h.
> > 
> > This fixes 5 headers_check warnings.
> > 
> How many times does this need to be NAKed?

Until someone gets a clue and puts comments in there explaining this?

  parent reply	other threads:[~2010-12-01 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 15:10 [PATCH 0/4] trivial header fixes Alexander Shishkin
2010-12-01 15:10 ` [PATCH 1/4] drm: fix headers to include linux/types.h Alexander Shishkin
2010-12-01 16:54   ` Julien Cristau
2010-12-01 17:37     ` Alexander Shishkin
2010-12-01 17:54     ` Kristian Høgsberg
2010-12-01 19:38     ` Andrew Morton [this message]
2010-12-01 19:55       ` [Intel-gfx] " Dave Airlie
2010-12-01 20:12         ` Randy Dunlap
2010-12-01 15:10 ` [PATCH 2/4] cramfs: hide function prototypes behind __KERNEL__ macro Alexander Shishkin
2010-12-01 15:10 ` [PATCH 3/4] scsi: fix a header to include linux/types.h Alexander Shishkin
2010-12-01 15:10 ` [PATCH 4/4] toshiba.h: hide a function prototypes behind __KERNEL__ macro Alexander Shishkin

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=20101201113841.46e92def.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jcristau@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtuoso@slind.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

Powered by JetHome