public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	sam@ravnborg.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v2] documentation: build source files in Documentation sub-dir
Date: Sun, 13 Apr 2008 16:05:05 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0804131602310.3261@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080410181153.92a5724d.akpm@linux-foundation.org>

On Thu, 10 Apr 2008, Andrew Morton wrote:
> >  struct ustat {
> > -	__kernel_daddr_t	f_tfree;
> > -	__kernel_ino_t		f_tinode;
> > +	daddr_t			f_tfree;
> > +	ino_t			f_tinode;
> >  	char			f_fname[6];
> >  	char			f_fpack[6];
> >  };
> 
> hm.
> 
> It'd be nice to know how git-x86 managed to make this happen.  I haven't
> looked, apart from noting that it doesn't seem to touch any of the relevant
> files.
 
Hmm, something must define __KERNEL_STRICT_NAMES to make this happen,
but there is nothing in the entire kernel tree which defines it.

Thanks,
	tglx

  reply	other threads:[~2008-04-13 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 19:45 [PATCH] documentation: build source files in Documentation sub-dir Randy Dunlap
2008-04-08 20:46 ` Andrew Morton
2008-04-09 19:35   ` [PATCH v2] " Randy Dunlap
2008-04-09 21:54     ` Andrew Morton
2008-04-11  0:56       ` Randy Dunlap
2008-04-11  1:11         ` Andrew Morton
2008-04-13 14:05           ` Thomas Gleixner [this message]
2008-04-09 22:52     ` Nick Andrew
2008-04-09 23:53       ` Randy Dunlap

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=alpine.LFD.1.10.0804131602310.3261@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.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