mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] uml-patch-2.6.7-2
Date: Wed, 08 Sep 2004 20:35:34 -0400	[thread overview]
Message-ID: <200409090035.i890ZYBP016288@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Sun, 05 Sep 2004 17:35:36 +0200." <200408251746.53523.blaisorblade_spam@yahoo.it>

blaisorblade_spam@yahoo.it said:
> * First, please do a "make clean" before releasing the patch. There
> are some  binaries included in it! And also semaphore.c, which is a
> symlink normally. 

I do.  It's just that make clean didn't catch everything.

> * About filehandle_switch: you deleted a line (probably by mistake).
> Reread  more carefully the separate patches you get with quilt: when
> you see the  other attached patch (uml-restore-lost-code.patch),
> you'll agree with me. 

Yuck, I have no idea how that happened.

> However, IMHO, since you cannot close and reopen a pipe, it's
> braindead that  the switch_pipe[] array is an array of filehandles.

Yeah, this is fixed in my 2.6 tree now.

				Jeff


  reply	other threads:[~2004-09-08 23:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19  3:00 uml-patch-2.6.7-2 Jeff Dike
2004-09-05 15:35 ` [uml-devel] uml-patch-2.6.7-2 BlaisorBlade
2004-09-09  0:35   ` Jeff Dike [this message]
2004-09-11 14:41     ` BlaisorBlade
     [not found] ` <413B76DB.5010600@pobox.com>
     [not found]   ` <200409061956.34557.blaisorblade_spam@yahoo.it>
2004-09-07 18:13     ` [uml-devel] Current state of UML - some help needed from mainline BlaisorBlade
2004-09-09  5:30       ` Jeff Garzik

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=200409090035.i890ZYBP016288@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade_spam@yahoo.it \
    --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

Powered by JetHome