linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Tony Finch <dot@dotat.at>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 11 (unifdef)
Date: Thu, 11 Nov 2010 09:48:32 -0800	[thread overview]
Message-ID: <20101111094832.827aaab3.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101111125655.15fa7188.sfr@canb.auug.org.au>

On Thu, 11 Nov 2010 12:56:55 +1100 Stephen Rothwell wrote:

> Hi all,
> 
> Changes since 20101110:


Hi Tony,
For the last week or so, linux-next tree has generated this warning:

unifdef: linux-next-20101111/X32/usr/include/xen/privcmd.h.tmp: 79: Premature EOF (#if line 33 depth 1)

linux/include/xen/privcmd.h contains:

#ifndef __user
#define __user
#endif

and linux/X32/usr/include/xen/privcmd.h contains:

#ifndef #define #endif

!!


Is this a problem with privcmd.h or unifdef or ???

thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-11-11 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  1:56 linux-next: Tree for November 11 Stephen Rothwell
2010-11-11 17:48 ` Randy Dunlap [this message]
2010-11-11 18:26   ` linux-next: Tree for November 11 (unifdef) Tony Finch
2010-11-11 18:44 ` [PATCH -next] staging/easycap: make module params private/static, fix build Randy Dunlap
2010-11-11 22:02   ` R.M. Thomas
2010-11-11 22:18     ` Randy Dunlap
2010-11-12 10:30       ` R.M. Thomas
2010-11-12 22:47 ` [PATCH -next] staging: fix ste_rmi4 build, depends on INPUT 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=20101111094832.827aaab3.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=dot@dotat.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).