* no-MMU build failure
@ 2013-02-28 20:08 Mark Salter
2013-02-28 20:14 ` Al Viro
0 siblings, 1 reply; 2+ messages in thread
From: Mark Salter @ 2013-02-28 20:08 UTC (permalink / raw)
To: Alexander Viro; +Cc: linux-next
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: no-MMU build failure
2013-02-28 20:08 no-MMU build failure Mark Salter
@ 2013-02-28 20:14 ` Al Viro
0 siblings, 0 replies; 2+ messages in thread
From: Al Viro @ 2013-02-28 20:14 UTC (permalink / raw)
To: Mark Salter; +Cc: linux-next
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...
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-02-28 20:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-28 20:08 no-MMU build failure Mark Salter
2013-02-28 20:14 ` Al Viro
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).