From: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
To: jdike@karaya.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ works
Date: Mon, 11 Jun 2007 13:26:10 +0300 [thread overview]
Message-ID: <466D2342.6010507@aladin.ro> (raw)
In-Reply-To: <1181514048.3157.9.camel@localhost>
*This message was transferred with a trial version of CommuniGate(r) Pro*
Eduard-Gabriel Munteanu wrote:
> The patch was written and tested on Linux 2.6.22-rc2-mm1.
Also tested on git. I forgot to tell you the diff is done against git
(it was made on that -mm, diffed, applied to git and then git-diffed
against HEAD).
next prev parent reply other threads:[~2007-06-11 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 22:20 [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ works Eduard-Gabriel Munteanu
2007-06-11 10:26 ` Eduard-Gabriel Munteanu [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-10 22:01 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
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=466D2342.6010507@aladin.ro \
--to=maxdamage@aladin.ro \
--cc=jdike@karaya.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