All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: linux-kernel@vger.kernel.org
Cc: atsl@ukc.ac.uk, mason@suse.com
Subject: Re: Possible patch for reiserfs-3.6.22 against 2.4.0-test12
Date: Tue, 12 Dec 2000 18:18:01 -0700	[thread overview]
Message-ID: <00121218180100.04636@localhost.localdomain> (raw)

Adam Sampson wrote:
>The latest reiserfs patch on ftp.namesys.com causes compilation errors
>against test12 due to the task queue changes. Does this look correct?
[patch snipped]
> 
>It does at least compile with these changes, but I haven't yet tested
>it. Looking at run_task_queue, it would appear that the while() is now
>redundant, but could someone who knows confirm/deny this?

Chris Mason is working on this.  In an earlier exchange on reiserfs-list:

Chris Mason wrote:
>I'll try to hack out a patch while I'm waiting, but the task struct changes
>are the least of our problems.  They've changed ll_rw_block to always set
>the end_io handler to the default one.  Since the journal code relies on
>being able to use its own end_io handler, this isn't good for us.  There is
>a new func we need to use instead, so I'm migrating over.
>
>Thew new stuff should be faster, so I won't complain ;-)

Your patch will probably let journal.c get compiled, but it might be dangerous
to use considering what Chris said.

Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-13  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13  1:18 Steven Cole [this message]
2000-12-13  1:22 ` Possible patch for reiserfs-3.6.22 against 2.4.0-test12 Adam Sampson
  -- strict thread matches above, loose matches on Subject: below --
2000-12-13  0:47 Adam Sampson
2000-12-13 13:14 ` Carlos E. Gorges
2000-12-13 15:08   ` Jorge Boncompte (DTI2)

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=00121218180100.04636@localhost.localdomain \
    --to=elenstev@mesatop.com \
    --cc=atsl@ukc.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    /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.