linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-next@vger.kernel.org, Chris Zankel <chris@zankel.net>
Subject: Re: xtensa: switch to generic clone()
Date: Tue, 27 Nov 2012 06:48:50 +0000	[thread overview]
Message-ID: <20121127064850.GE4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAMo8BfLK4syxXEjwWXixdxMaPrVgec1u7pTHqTvWO4zfpYLEsw@mail.gmail.com>

On Tue, Nov 27, 2012 at 08:48:24AM +0300, Max Filippov wrote:
> Hi Al,
> 
> looks like the following hunk is missing in the commit
>   a4bcde6 xtensa: switch to generic clone()
> found in the linux-next tree next-20121126, which breaks xtensa builds.
> 
> ---
> diff --git a/arch/xtensa/include/asm/syscall.h
> b/arch/xtensa/include/asm/syscall.h
> index b00c928..cd53ec2 100644
> --- a/arch/xtensa/include/asm/syscall.h
> +++ b/arch/xtensa/include/asm/syscall.h
> @@ -8,6 +8,8 @@
>   * Copyright (C) 2001 - 2007 Tensilica Inc.
>   */
> 
> +#include <asm-generic/syscalls.h>

The bug is real, all right, but I'm not sure I like that fix.
The problem hits in arch/xtensa/kernel/syscall.c, right?  I'd rather
get correct declaration into include/linux/syscalls.h and drop the
asm-generic/syscalls.h one.  I'll do it that way the next time I
push into for-next (in the morning, that is); for now your variant
will do as a temporary fix, of course.

Incidentally, xtensa_shmat() looks very similar to sys_shmat().  The
only difference is force_successful_syscall_return() in the latter
and that expands to do { } while (0) on xtensa (i.e. default gets used).
Granted, I'm half asleep right now and could've easily missed something,
but...

      reply	other threads:[~2012-11-27  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  5:48 xtensa: switch to generic clone() Max Filippov
2012-11-27  6:48 ` 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=20121127064850.GE4939@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=chris@zankel.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-next@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).