From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [RFC] x86: bitops asm constraint fixes
Date: Thu, 27 Mar 2008 09:41:30 +0100 [thread overview]
Message-ID: <20080327084130.GG15626@elte.hu> (raw)
In-Reply-To: <47EB56E0020000780004917E@public.id2-vpn.continvity.gns.novell.com>
* Jan Beulich <jbeulich@novell.com> wrote:
> Please revert it for the time being, I've got a better version (i.e.
> without extra dead code being generated) that I intended to submit
> once I know whether the other issues pointed out in the description on
> the original patch also should be adjusted. Of course, that could also
> be done incrementally, but I would think overhauling the whole file at
> once wouldn't be a bad thing...
since it appears to cause no problems in x86.git (it passed a lot of
testing already) i'd prefer to keep it (so that we can see any other
side-effects of touching this code) - could you send your improvements
as a delta against x86.git/latest? [or is there any outright bug caused
by your changes that necessiates a revert?]
Ingo
next prev parent reply other threads:[~2008-03-27 8:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 8:12 [RFC] x86: bitops asm constraint fixes Jan Beulich
2008-03-27 8:41 ` Ingo Molnar [this message]
2008-04-14 12:53 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 13:31 Jan Beulich
2008-04-14 16:21 ` Jeremy Fitzhardinge
2008-04-15 7:03 ` Jan Beulich
2008-03-28 19:55 Jan Beulich
2008-03-13 9:08 Jan Beulich
2008-03-14 7:51 ` H. Peter Anvin
2008-03-14 8:09 ` Jan Beulich
2008-03-14 18:56 ` Jeremy Fitzhardinge
2008-03-17 9:08 ` Jan Beulich
2008-03-14 21:07 ` Chuck Ebbert
2008-03-17 9:16 ` Jan Beulich
2008-03-19 13:19 ` H. Peter Anvin
2008-03-21 13:54 ` Ingo Molnar
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=20080327084130.GG15626@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.