From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mark Salter <msalter@redhat.com>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: Re: no-MMU build failure
Date: Thu, 28 Feb 2013 20:14:16 +0000 [thread overview]
Message-ID: <20130228201416.GR4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1362082104.7319.13.camel@t520.redhat.com>
On Thu, Feb 28, 2013 at 03:08:24PM -0500, Mark Salter wrote:
> I'm seeing a build failure in linux-next for c6x (no-MMU):
>
> /linux-next/mm/shmem.c: In function 'shmem_file_setup':
> /linux-next/mm/shmem.c:2936:2: error: 'error' undeclared (first use in this function)
Yechh... My fault; I think the cleanest fix here is
res = ERR_PTR(ramfs_nommu_expand_for_mapping(inode, size));
if (res)
goto put_dentry;
Will be fixed in the next signal.git pull...
prev parent reply other threads:[~2013-02-28 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:08 no-MMU build failure Mark Salter
2013-02-28 20:14 ` Al Viro [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=20130228201416.GR4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-next@vger.kernel.org \
--cc=msalter@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.