All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Daniel Stone <daniel@kabuki.sfarc.net>
Cc: Daniel Podlejski <underley@underley.eu.org>,
	linux-kernel@vger.kernel.org
Subject: Re: XFS and Alan kernel tree
Date: Wed, 13 Jun 2001 09:03:16 +1000	[thread overview]
Message-ID: <13436.992386996@ocs4.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 13 Jun 2001 08:25:52 +1000." <20010613082551.A3032@kabuki.openfridge.net>

On Wed, 13 Jun 2001 08:25:52 +1000, 
Daniel Stone <daniel@kabuki.sfarc.net> wrote:
>On Sat, May 05, 2001 at 11:08:16PM +0200, Daniel Podlejski wrote:
>> I merge XFS witch Alan tree (2.4.4-ac5). It's seems to be stable.
>> Patch against Alan tree is avaliable at:
>
>Hi Daniel,
>I've got a KDB patch against a relatively recent 2.4.5-ac6, but are you
>still continuing your porting effort to the -ac series?

kdb v1.8-2.4.5-ac6 works for -ac6 through -ac13.  None of the changes
in that series affect kdb.

There have been some significant changes to page I/O handling in
2.4.6-pre[12] which are reflected in the XFS CVS tree.  -ac13 is still
using the old page_launder() code which is not as clean.  In addition
kdb for Linus's and AC's trees has diverged quite a bit because of the
console and NMI cleanup in -ac.  Fitting XFS from CVS into -ac13 will
be very nasty, you might want to wait until AC syncs to Linus's kernel
or Linus takes some of the -ac changes.


  reply	other threads:[~2001-06-12 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 21:08 XFS and Alan kernel tree Daniel Podlejski
2001-05-06  2:29 ` Keith Owens
2001-05-06 21:54 ` Norbert Tretkowski
2001-06-12 22:25 ` Daniel Stone
2001-06-12 23:03   ` Keith Owens [this message]
2001-06-12 23:15     ` Daniel Stone
2001-06-13  2:40       ` Shawn

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=13436.992386996@ocs4.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=daniel@kabuki.sfarc.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=underley@underley.eu.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 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.