From: Chris Metcalf <cmetcalf@tilera.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build failure after merge of the final tree (tile tree related)
Date: Mon, 07 Jun 2010 08:56:57 -0400 [thread overview]
Message-ID: <4C0CEC99.3020909@tilera.com> (raw)
In-Reply-To: <20100607140140.870c0fb5.sfr@canb.auug.org.au>
On 6/7/2010 12:01 AM, Stephen Rothwell wrote:
> I applied this patch for today. Something better could probably be
> done. I note that there is already a declaration of sys_rt_sigaction in
> include/asm-generic/syscalls.h ...
>
Yes, thanks for the pointer. In fact by adjusting a couple of tile
syscalls slightly I can just use <asm-generic/syscalls.h> wholesale. I
reverted the addition of sys_rt_sigaction() and sys_rt_sigsuspend() to
<linux/syscalls.h> and cleaned up the arch/tile/include/asm/syscalls.h
as well. I mailed the patch as another reply-to to Stephen's original
message.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2010-06-07 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 4:01 linux-next: build failure after merge of the final tree (tile tree related) Stephen Rothwell
2010-06-07 12:48 ` [PATCH] Revert adding some arch-specific signal syscalls to <linux/syscalls.h> Chris Metcalf
2010-06-07 13:18 ` Arnd Bergmann
2010-06-07 12:56 ` Chris Metcalf [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 3:42 linux-next: build failure after merge of the final tree (tile tree related) Stephen Rothwell
2011-05-24 12:25 ` Chris Metcalf
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=4C0CEC99.3020909@tilera.com \
--to=cmetcalf@tilera.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).