From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [PATCH] UML - forgot asm-um/cmpxchg.h
Date: Thu, 3 May 2007 10:14:05 -0400 [thread overview]
Message-ID: <20070503141405.GA5522@c2.user-mode-linux.org> (raw)
In-Reply-To: <20070502230919.cb6864df.akpm@linux-foundation.org>
On Wed, May 02, 2007 at 11:09:19PM -0700, Andrew Morton wrote:
> OK, I clumped all three patches into one as I think that's required for
> git-bisect friendliness.
OK - I separated the i386 and x86_64 bits to make it easy to drop the
x86_64 part.
Plus, I think it doesn't make any difference - the headers behave the
same as seen from the outside, except that UML needs the uml-cmpxchg
patch in order to build. So, putting that first, then the other two
separately results in a patchset that builds at all stages, I believe.
Jeff
--
Work email - jdike at linux dot intel dot com
prev parent reply other threads:[~2007-05-03 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 19:36 [PATCH] UML - forgot asm-um/cmpxchg.h Jeff Dike
2007-05-03 6:09 ` Andrew Morton
2007-05-03 14:14 ` Jeff Dike [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=20070503141405.GA5522@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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