From: Jeff Dike <jdike@addtoit.com>
To: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ works
Date: Tue, 12 Jun 2007 09:26:52 -0400 [thread overview]
Message-ID: <20070612132652.GA5267@c2.user-mode-linux.org> (raw)
In-Reply-To: <466E32C5.70105@aladin.ro>
On Tue, Jun 12, 2007 at 08:44:37AM +0300, Eduard-Gabriel Munteanu wrote:
> Okay, I don't have an x86_64, sparc64 or something similar, as my
> computer is an x86, so I can't contradict this. If everything is fine on
> such arches, no fix is needed when nothing's broken... though I still
> think it's kind of ugly (though it's somehow ingenious as a hack) :)
Yeah, I would agree with that.
> Do you want me to resubmit the patch without these changes? I'll be back
> in a few hours (got to go now) and trim this out from the patch if
> that's necessary.
I have it in my tree now, without that set of changes. If you want to
make the change yourself, send me a new patch, and I'll use it.
Otherwise, I'll stick with what I have now.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2007-06-12 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 22:01 [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ works Eduard-Gabriel Munteanu
2007-06-11 17:31 ` Jeff Dike
2007-06-11 19:39 ` Eduard-Gabriel Munteanu
2007-06-11 21:16 ` Jeff Dike
2007-06-11 22:39 ` Eduard-Gabriel Munteanu
2007-06-12 0:48 ` Jeff Dike
2007-06-12 5:44 ` Eduard-Gabriel Munteanu
2007-06-12 13:26 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-10 22:20 Eduard-Gabriel Munteanu
2007-06-11 10:26 ` Eduard-Gabriel Munteanu
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=20070612132652.GA5267@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxdamage@aladin.ro \
/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.