public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
To: Jeff Dike <jdike@addtoit.com>
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 08:44:37 +0300	[thread overview]
Message-ID: <466E32C5.70105@aladin.ro> (raw)
In-Reply-To: <20070612004804.GA9871@c2.user-mode-linux.org>

*This message was transferred with a trial version of CommuniGate(r) Pro*
Jeff Dike wrote:
> No it won't.  UML builds without warnings here on x86_64.

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) :)

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.

  reply	other threads:[~2007-06-12  5:44 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 [this message]
2007-06-12 13:26             ` Jeff Dike
  -- 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=466E32C5.70105@aladin.ro \
    --to=maxdamage@aladin.ro \
    --cc=jdike@addtoit.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