All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH][CFT] Re: 2.4.15-pre9 breakage (inode.c)
Date: Fri, 23 Nov 2001 22:34:12 +0000	[thread overview]
Message-ID: <20011123223412.B3141@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0111231634310.2422-100000@weyl.math.psu.edu> <Pine.GSO.4.21.0111231701440.2422-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0111231701440.2422-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Fri, Nov 23, 2001 at 05:06:46PM -0500

On Fri, Nov 23, 2001 at 05:06:46PM -0500, Alexander Viro wrote:
> On Fri, 23 Nov 2001, Alexander Viro wrote:
> > 	Untested fix follows.  And please, pass the brown paperbag... ;-/
> 
> ... and now for something that really builds:

I can confirm this passes my boot, shutdown, reboot test that failed with
2.4.15-greased-turkey.  2.4.15-viro1 is currently running my kernel build
tests quite happily thus far.

I think 2.4.15-greased-turkey should be renamed to 2.4.15-dead-duck. 8)

Al, thanks for the fast response.  Appologies for the slow build.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-11-23 22:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 21:22 2.4.15-pre9 breakage (inode.c) Alexander Viro
2001-11-23 21:42 ` Jeff Merkey
2001-11-23 21:51 ` [PATCH][CFT] " Alexander Viro
2001-11-23 22:06   ` Alexander Viro
2001-11-23 22:34     ` Russell King [this message]
2001-11-23 22:35     ` Phil Sorber
2001-11-23 22:49       ` Alexander Viro
2001-11-23 23:05     ` Andreas Dilger
2001-11-23 23:35       ` Russell King
2001-11-24  1:48       ` Linus Torvalds
2001-11-24  5:47 ` Andrea Arcangeli
2001-11-24  5:55   ` Linus Torvalds
2001-11-24  6:08     ` Alexander Viro
2001-11-24  6:26       ` Andrea Arcangeli
2001-11-24  6:31         ` Alexander Viro
2001-11-24  6:37           ` Alexander Viro
2001-11-24  6:50             ` Andrea Arcangeli
2001-11-24  6:58               ` Alexander Viro
2001-11-24  7:01               ` Andrea Arcangeli
2001-11-24  7:06                 ` Alexander Viro
2001-11-24  7:12                   ` Andrea Arcangeli
2001-11-24  7:30                     ` Alexander Viro
2001-11-24  7:44                       ` Andrea Arcangeli
2001-11-24  8:05                         ` Alexander Viro
2001-11-24  8:21                           ` Andrea Arcangeli
2001-11-24  8:38                             ` Alexander Viro
2001-11-24  9:38                               ` Andrea Arcangeli
2001-11-24  9:56                                 ` Alexander Viro
2001-11-24 10:25                                   ` Andrea Arcangeli
2001-11-24  6:44           ` Andrea Arcangeli
2001-11-24  6:51             ` Alexander Viro
2001-11-24  9:00     ` Russell King
2001-11-24 10:20     ` Christian Bornträger
2001-11-24  6:04   ` Alexander Viro
2001-11-24  6:20     ` Andrea Arcangeli
2001-11-24  6:29       ` Alexander Viro

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=20011123223412.B3141@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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.