From: Mark Salter <msalter@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: no-MMU build failure
Date: Thu, 28 Feb 2013 15:08:24 -0500 [thread overview]
Message-ID: <1362082104.7319.13.camel@t520.redhat.com> (raw)
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)
Looks like it is due to this commit:
commit 6b4d0b2793337cc8943cd2948388218e2777400c
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Thu Feb 14 21:37:26 2013 -0500
clean shmem_file_setup() a bit
--Mark
next reply other threads:[~2013-02-28 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:08 Mark Salter [this message]
2013-02-28 20:14 ` no-MMU build failure Al Viro
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=1362082104.7319.13.camel@t520.redhat.com \
--to=msalter@redhat.com \
--cc=linux-next@vger.kernel.org \
--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 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.