public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	ajoshi@kernel.crashing.org, bcollins@debian.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-pre5
Date: Thu, 27 Feb 2003 09:32:39 +0100	[thread overview]
Message-ID: <20030227083238.GS7685@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.53L.0302270314050.1433@freak.distro.conectiva>

On Thu, Feb 27, 2003 at 03:14:44AM -0300, Marcelo Tosatti wrote:
> 
> So here goes -pre5.
> 
> 
> Summary of changes from v2.4.21-pre4 to v2.4.21-pre5
> ============================================
> 
> <ajoshi@kernel.crashing.org>:
>   o rivafb 0.9.4 update
>...

WTF is this???

Besides the rivafb update it reverts parts of the IEEE 1394 patches that 
were included in -pre4.


Please revert these bogus changes.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2003-02-27  8:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  6:14 Linux 2.4.21-pre5 Marcelo Tosatti
2003-02-27  8:24 ` Christoph Hellwig
2003-02-27  8:32 ` Adrian Bunk [this message]
2003-02-27 12:40   ` Ben Collins
2003-02-27 19:22     ` ajoshi
2003-02-27 19:35       ` Ben Collins
2003-03-11 23:39         ` Marcelo Tosatti
2003-02-27  8:53 ` Christoph Hellwig
2003-02-27  9:39 ` Ben Lau
2003-02-27 10:19   ` Simon Oosthoek
2003-02-27 10:48     ` Benjamin Herrenschmidt
2003-02-27 11:43       ` Simon Oosthoek
2003-02-28  5:46       ` Ben Lau
2003-02-27 23:26 ` [patch] 2.4.21-pre5: fix Auerswald compile Adrian Bunk
2003-02-28  7:47   ` Wolfgang Mües
2003-03-05 22:02   ` Greg KH
2003-03-07  2:47 ` Linux 2.4.21-pre5 J.A. Magallon

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=20030227083238.GS7685@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=ajoshi@kernel.crashing.org \
    --cc=bcollins@debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox