On Thu, Mar 1, 2012 at 9:41 PM, Mark Salter <msalter@xxxxxxxxxx> wrote:
> In linux-next, this breaks nommu builds:
>
> commit b8665bd461ecdc561e7c95d039567d0a79208226
> Author: Siddhesh Poyarekar <siddhesh.poyarekar@xxxxxxxxx>
> Date: Sat Feb 25 12:28:09 2012 +1100
>
> procfs: mark thread stack correctly in proc/<pid>/maps
>
> I think this was merged into linux-next from the -mm tree.
>
> There are unbalanced parens in fs/proc/task_nommu.c which leads to this
> when building:
>
> fs/proc/task_nommu.c: In function 'nommu_vma_show':
> fs/proc/task_nommu.c:177:2: warning: no return statement in function returning non-void
> fs/proc/task_nommu.c: At top level:
> fs/proc/task_nommu.c:179:14: error: expected ')' before '\xa'
> fs/proc/task_nommu.c:180:2: error: expected identifier or '(' before 'return'
> fs/proc/task_nommu.c:181:1: error: expected identifier or '(' before '}' token
>
Sorry about that. My latest patch submission to procfs happens to fix this:
https://lkml.org/lkml/2012/3/1/4
Do you need a separate submission that fixes just this build failure?
--
Siddhesh Poyarekar
http://siddhesh.in
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
