mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 1/1] uml-update-2.6.8-finish
Date: Sat, 11 Sep 2004 17:40:12 +0200	[thread overview]
Message-ID: <200409111740.12121.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200409102103.i8AL3b0O004288@ccure.user-mode-linux.org>

On Friday 10 September 2004 23:03, Jeff Dike wrote:
> blaisorblade_personal@yahoo.it said:
> > About the one from Jeff Dike, it's dangerous because I don't know
> > whether or  not we would see any introduced bug.

> The ghash removal?  That's necessary, for one, and that code isn't
> currently used anyway, so any bugs that I introduced can be sorted out
> later.  For now, it's sufficient that it compiles.
And making it compile with the hash code, rather than the rb_tree one? I know 
ghash.h must be removed, but there is no reason at all to switch to Red-Black 
trees. Even because, later, we will just see "Hey, I get a panic here" + 
backtrace. Doing things right in first place is better.

Andrew, what's your opinion about this? Do you prefer staying with the same 
code (but without having a ghash.h) or using the new one?

My idea is to move the needed #defines (not everything) inside physmem.c for 
now, so that ghash.h does not appear in 2.6.9; then, after fixing the 
breakage for mainline, we can look at the code to see if it needs any change; 
however that should be tested for a while (probably in Jeff Dike's tree, 
which is going to become for experimental stuff, now that UML gets merged in 
mainline).

Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729

  parent reply	other threads:[~2004-09-11 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 17:38 blaisorblade_spam
2004-09-10 18:59 ` [uml-devel] " BlaisorBlade
     [not found] ` <200409102028.54580.blaisorblade_personal@yahoo.it>
     [not found]   ` <200409102103.i8AL3b0O004288@ccure.user-mode-linux.org>
2004-09-11 15:40     ` BlaisorBlade [this message]
2004-09-11 18:15       ` Jeff Dike
2004-09-11 17:47         ` BlaisorBlade

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=200409111740.12121.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®