From: James Hogan <james.hogan@imgtec.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
James Hogan <james.hogan@imgtec.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: Tree for Feb 4
Date: Mon, 4 Feb 2013 13:56:32 +0000 [thread overview]
Message-ID: <CAAG0J99hxOOGh74wQ2R47o0noRxQhNS8T_DNnbX2FX-rJ2wMzQ@mail.gmail.com> (raw)
In-Reply-To: <20130204183926.f5d5ab14b0ae4d22cb253202@canb.auug.org.au>
Hi Stephen,
On 4 February 2013 07:39, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Merging signal/for-next (9005965 x86: convert to ksignal)
> CONFLICT (content): Merge conflict in arch/x86/Kconfig
I think this conflict has been resolved incorrectly.
Al's commit 1820f96 "burying unused conditionals" removed
GENERIC_SIGALTSTACK from config X86, but the merge
(c5395e2affed5c42200cb6e21e3380995ef22ae3) left GENERIC_SIGALTSTACK
in:
diff --cc arch/x86/Kconfig
index 32d4ff1,49fb44e..6979498
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@@ -114,9 -113,9 +114,12 @@@ config X8
select MODULES_USE_ELF_REL if X86_32
select MODULES_USE_ELF_RELA if X86_64
select CLONE_BACKWARDS if X86_32
+ select ARCH_USE_BUILTIN_BSWAP
+ select GENERIC_SIGALTSTACK
+ select ARCH_USE_BUILTIN_BSWAP
+ select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION
+ select OLD_SIGACTION if X86_32
+ select COMPAT_OLD_SIGACTION if IA32_EMULATION
config INSTRUCTION_DECODER
def_bool y
Cheers
James
next prev parent reply other threads:[~2013-02-04 13:56 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 7:39 linux-next: Tree for Feb 4 Stephen Rothwell
2013-02-04 13:56 ` James Hogan [this message]
2013-02-04 20:33 ` Stephen Rothwell
2014-02-04 5:07 Stephen Rothwell
[not found] ` <CAP=VYLpgLC_4yuPtQH_yAd8S9cqQAVu2uB2=Wf3q_zgY4uzkLw@mail.gmail.com>
2014-02-04 22:23 ` Stephen Rothwell
2014-02-05 0:41 ` Stephen Rothwell
2015-02-04 8:35 Stephen Rothwell
2015-02-04 12:26 ` Sedat Dilek
2015-02-04 15:16 ` Jens Axboe
2015-02-04 15:21 ` Sedat Dilek
2015-02-04 15:31 ` Jens Axboe
2015-02-04 15:36 ` Sedat Dilek
2015-02-04 15:58 ` Martin K. Petersen
2015-02-04 16:06 ` Sedat Dilek
2015-02-05 3:17 ` Martin K. Petersen
2015-02-05 3:41 ` Sedat Dilek
2015-02-05 19:46 ` Sedat Dilek
2015-02-06 15:24 ` Sedat Dilek
2015-02-04 20:18 ` Sedat Dilek
2015-02-04 21:54 ` Rafael J. Wysocki
2015-02-04 21:53 ` Paul E. McKenney
2015-02-04 22:59 ` Rafael J. Wysocki
2015-02-04 23:51 ` Paul E. McKenney
2015-02-04 23:58 ` Sedat Dilek
2015-02-05 0:10 ` Paul E. McKenney
2015-02-05 0:30 ` Sedat Dilek
2015-02-05 0:57 ` Paul E. McKenney
2015-02-05 1:18 ` Sedat Dilek
2015-02-05 1:51 ` Paul E. McKenney
2015-02-05 1:53 ` Sedat Dilek
2015-02-05 2:12 ` Sedat Dilek
2015-02-05 4:13 ` Paul E. McKenney
2015-02-05 7:14 ` Dave Hansen
2015-02-05 14:37 ` Paul E. McKenney
2015-02-05 14:57 ` Sedat Dilek
2015-02-05 16:58 ` Paul E. McKenney
2015-02-05 18:03 ` Steven Rostedt
2015-02-05 18:08 ` Steven Rostedt
2015-02-05 18:11 ` Dave Hansen
2015-02-05 18:34 ` Paul E. McKenney
2015-02-05 18:35 ` Dave Hansen
2015-02-05 18:45 ` Paul E. McKenney
2015-02-05 19:25 ` Sedat Dilek
2015-02-05 19:33 ` Paul E. McKenney
2015-02-05 19:42 ` Sedat Dilek
2015-02-05 19:58 ` Steven Rostedt
2015-02-05 20:07 ` Sedat Dilek
2015-02-05 20:22 ` Steven Rostedt
2015-02-05 20:50 ` Sedat Dilek
2015-02-05 21:45 ` Sedat Dilek
2015-02-05 22:09 ` Steven Rostedt
2015-02-05 22:16 ` Sedat Dilek
2015-02-05 23:11 ` Steven Rostedt
2015-02-05 23:53 ` Sedat Dilek
2015-02-06 0:03 ` Sedat Dilek
2015-02-06 0:12 ` Steven Rostedt
2015-02-06 0:14 ` Sedat Dilek
2015-02-04 22:38 ` Sedat Dilek
2015-02-04 23:25 ` Rafael J. Wysocki
2015-02-04 23:54 ` Sedat Dilek
2015-02-04 22:46 ` Sedat Dilek
2015-02-04 23:30 ` Rafael J. Wysocki
2015-02-04 23:48 ` Sedat Dilek
2016-02-04 3:48 Stephen Rothwell
2019-02-04 5:35 Stephen Rothwell
2020-02-04 4:19 Stephen Rothwell
2021-02-04 9:13 Stephen Rothwell
2022-02-04 4:14 Stephen Rothwell
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=CAAG0J99hxOOGh74wQ2R47o0noRxQhNS8T_DNnbX2FX-rJ2wMzQ@mail.gmail.com \
--to=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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).