From: Andi Kleen <ak@suse.de>
To: Joe Korty <joe.korty@ccur.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] strange work_notifysig code since 2.6.16
Date: 25 Oct 2006 21:02:58 +0200 [thread overview]
Message-ID: <p73r6wwkyl9.fsf@verdi.suse.de> (raw)
In-Reply-To: <20061025142923.GA20833@tsunami.ccur.com>
Joe Korty <joe.korty@ccur.com> writes:
> > I suspect this won't link with CONFIG_VM86 disabled because save_v86_state
> > goes away. I think we just need to move the #endif up a few lines.
>
> Hi Matt,
> Since that also makes the 'then' and 'else' branches identical, perhaps
> this patch would be better .. it eliminates the VM86 test entirely when
> CONFIG_VM86=n.
>
> Boot tested with CONFIG_VM86=y.
Added.
-Andi
prev parent reply other threads:[~2006-10-25 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 23:19 [PATCH] strange work_notifysig code since 2.6.16 Joe Korty
2006-10-25 5:48 ` Matt Mackall
2006-10-25 14:29 ` Joe Korty
2006-10-25 19:02 ` Andi Kleen [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=p73r6wwkyl9.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@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