All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patches in 2.4.17-pre2 that aren't in 2.5.1-pre8
Date: Mon, 10 Dec 2001 12:43:53 +0100	[thread overview]
Message-ID: <3C149FF9.407@epfl.ch> (raw)
In-Reply-To: <linux.kernel.E16DNNu-0001VB-00@the-village.bc.nu>

Hello all



> 
> In many cases that isnt true, and for a lot of the pending patches its
> pointless merging them into 2.5 until 2.5 gets into better shape. Going back
> over them as you have done is something that does need doing, but not until
> the block layer has some semblance of completion about it

Well I just saw the opposite ;-) ... A patch I had submitted a few weeks 
ago for Intel 830MP agp support has been intgrated in 2.5.1-pre3, but is 
still not in the 2.4 branch... Several users have reported success with 
this patch, so unless somebody shows storng opposition, I would suggest 
to merge it...
Get it here : http://ltswww.epfl.ch/~aspert/patches/patch-agp_i830mp-2.4.16

Best regards
-- 
Nicolas Aspert      Signal Processing Laboratory (LTS)
Swiss Federal Institute of Technology (EPFL)


       reply	other threads:[~2001-12-10 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <linux.kernel.E16DNNu-0001VB-00@the-village.bc.nu>
2001-12-10 11:43 ` Nicolas Aspert [this message]
2001-12-10 15:53   ` Patches in 2.4.17-pre2 that aren't in 2.5.1-pre8 Marcelo Tosatti
2001-12-10 17:22     ` Nicolas Aspert
2001-12-10 17:30     ` Alan Cox
2001-12-10 18:18     ` Robert Love
2001-12-10 17:13       ` Marcelo Tosatti
2001-12-10 18:47       ` Stephan von Krawczynski
2001-12-10  9:51 Adrian Bunk
2001-12-10 10:10 ` Alan Cox

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=3C149FF9.407@epfl.ch \
    --to=nicolas.aspert@epfl.ch \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.