All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: David Miller <davem@davemloft.net>
Cc: vonbrand@inf.utfsm.cl, torvalds@osdl.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.20-rc2: known unfixed regressions
Date: Fri, 29 Dec 2006 13:58:28 +0100	[thread overview]
Message-ID: <20061229125828.GR20714@stusta.de> (raw)
In-Reply-To: <20061228.205106.130845178.davem@davemloft.net>

On Thu, Dec 28, 2006 at 08:51:06PM -0800, David Miller wrote:
> From: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
> Date: Thu, 28 Dec 2006 22:36:02 -0300
> 
> > Adrian Bunk <bunk@stusta.de> wrote:
> > > This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> > 
> > Add that on SPARC64 boot fails due to missing /dev/root. Vanilla 2.6.19 and
> > 2.6.19.1 work fine, before 2.6.20-rc1 it broke. I checked the initrds for
> > both versions, the only difference "diff -Nur" finds between the unpacked
> > initrds are the modules themselves (obviously).
> 
> Did you report this will all relevant details on sparclinux@vger
> so that the sparc64 maintainers can analyze the problem?
> 
> I didn't see the report there else I would be looking into it.
>...

I did copy the email to both sparclinux and you when I asked Horst 
whether it's still present in the latest kernel, and therefore his 
answer that it does the day before yesterday should have reached you.

The thread is "Re: 2.6.19 (current from git) on SPARC64: Can't mount /".

Is there anything I can improve to catch your intention?
Is "reply with fullquote + question + adding Cc's" somehow suboptimal?

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


  reply	other threads:[~2006-12-29 12:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  4:49 Linux 2.6.20-rc2 Linus Torvalds
2006-12-24 13:58 ` Alessandro Suardi
2006-12-24 14:49   ` Jeff Garzik
2006-12-24 17:13 ` Andreas Schwab
2006-12-25 21:02 ` swsusp testing wanted (was Re: Linux 2.6.20-rc2) Pavel Machek
2006-12-28 22:31 ` 2.6.20-rc2: known regressions with patches available Adrian Bunk
2006-12-28 22:31   ` Adrian Bunk
2006-12-28 22:39 ` 2.6.20-rc2: known unfixed regressions Adrian Bunk
2006-12-28 22:57   ` Greg KH
2006-12-28 23:07     ` Adrian Bunk
2006-12-28 23:17       ` Linus Torvalds
2006-12-28 23:30         ` Greg KH
2006-12-29  1:36   ` Horst H. von Brand
2006-12-29  4:51     ` David Miller
2006-12-29 12:58       ` Adrian Bunk [this message]
2006-12-29 12:53     ` Adrian Bunk
2006-12-29 18:07   ` Ben Collins
2006-12-29 19:25     ` Adrian Bunk
2006-12-30  1:21       ` Horst H. von Brand
2006-12-30  1:57         ` Adrian Bunk
2006-12-29 18:14   ` Daniel Barkalow
2006-12-29 19:22     ` Adrian Bunk
2006-12-29 20:18       ` Daniel Barkalow
2006-12-31  0:47 ` 2.6.20-rc2: known unfixed regressions (v2) Adrian Bunk
2006-12-31  0:47   ` Adrian Bunk
2006-12-31  0:47   ` Adrian Bunk
2006-12-31  9:44   ` Ismail Dönmez
2006-12-31  9:44     ` Ismail Dönmez
2006-12-31  9:44     ` Ismail Dönmez

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=20061229125828.GR20714@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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.