From: Adam Sampson <ats1@ukc.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Possible patch for reiserfs-3.6.22 against 2.4.0-test12
Date: 13 Dec 2000 00:47:57 +0000 [thread overview]
Message-ID: <873dftywn6.fsf@cartman.azz.net> (raw)
Hiya.
The latest reiserfs patch on ftp.namesys.com causes compilation errors
against test12 due to the task queue changes. Does this look correct?
--- fs/reiserfs/journal.c.orig Wed Dec 13 00:13:00 2000
+++ fs/reiserfs/journal.c Wed Dec 13 00:40:52 2000
@@ -1762,7 +1762,7 @@
ct->p_s_sb = p_s_sb ;
ct->jindex = jindex ;
ct->task_done = NULL ;
- ct->task.next = NULL ;
+ INIT_LIST_HEAD(&ct->task.list);
ct->task.sync = 0 ;
ct->task.routine = (void *)(void *)reiserfs_journal_commit_task_func ;
ct->self = ct ;
@@ -1813,7 +1813,7 @@
lock_kernel() ;
while(1) {
- while(reiserfs_commit_thread_tq) {
+ while(TQ_ACTIVE(reiserfs_commit_thread_tq)) {
run_task_queue(&reiserfs_commit_thread_tq) ;
}
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?
--
Adam Sampson
azz@gnu.org
-
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/
next reply other threads:[~2000-12-13 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 0:47 Adam Sampson [this message]
2000-12-13 13:14 ` Possible patch for reiserfs-3.6.22 against 2.4.0-test12 Carlos E. Gorges
2000-12-13 15:08 ` Jorge Boncompte (DTI2)
2000-12-13 1:18 Steven Cole
2000-12-13 1:22 ` Adam Sampson
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=873dftywn6.fsf@cartman.azz.net \
--to=ats1@ukc.ac.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).