public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Richard Weinberger <richard@nod.at>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Jeff Dike <jdike@addtoit.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: linux-next: Tree for June 27 (uml)
Date: Mon, 27 Jun 2011 10:01:19 -0700	[thread overview]
Message-ID: <20110627100119.9bebaa5b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110627164259.GF11013@ZenIV.linux.org.uk>

On Mon, 27 Jun 2011 17:42:59 +0100 Al Viro wrote:

> On Mon, Jun 27, 2011 at 06:30:43PM +0200, Richard Weinberger wrote:
> > Am Montag 27 Juni 2011, 17:27:33 schrieb Randy Dunlap:
> > > On Mon, 27 Jun 2011 16:16:56 +1000 Stephen Rothwell wrote:
> > > > Hi all,
> > > 
> > > > Changes since 20110624:
> > > uml defconfig builds on x86 (32-bit and 64-bit) fail with:
> > > 
> > > fs/hostfs/hostfs_kern.c:756: error: 'mask' undeclared (first use in this
> > > function)
> > 
> > Hmm, "->permission() sanitizing: don't pass flags to ->permission()" is the evil doer.
> > Al?
> 
> Gyah... s/mask/desired/ in that line.  Will fold...

Ack, that works, thanks.

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

      reply	other threads:[~2011-06-27 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  6:16 linux-next: Tree for June 27 Stephen Rothwell
2011-06-27 15:27 ` linux-next: Tree for June 27 (uml) Randy Dunlap
2011-06-27 16:30   ` Richard Weinberger
2011-06-27 16:42     ` Al Viro
2011-06-27 17:01       ` Randy Dunlap [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=20110627100119.9bebaa5b.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=sfr@canb.auug.org.au \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=viro@ZenIV.linux.org.uk \
    /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