public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mohammad A. Haque" <mhaque@haque.net>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Alexander Viro <viro@math.psu.edu>,
	Linus Torvalds <torvalds@transmeta.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] inode dirty blocks
Date: Mon, 04 Dec 2000 21:49:22 -0500	[thread overview]
Message-ID: <3A2C57B2.57DA3BA6@haque.net> (raw)
In-Reply-To: <3A2B9B39.AA240475@uow.edu.au> <Pine.GSO.4.21.0012040843490.5153-100000@weyl.math.psu.edu> <3A2C493C.4A321797@uow.edu.au>

Cool. Anyone have have a unified patch against pre4 or should I start
digging through my mail? =)

Andrew Morton wrote:
> This is with
> 
>         - test12-pre4
>         - aviro bforget patch
>         - UnlockPage() removed from vmscan.c:623
>         - and
> 
> --- linux-2.4.0-test12-pre4/fs/ext2/inode.c     Mon Dec  4 21:07:12 2000
> +++ linux-akpm/fs/ext2/inode.c  Tue Dec  5 08:46:38 2000
> @@ -1208,7 +1208,7 @@
>                 raw_inode->i_block[0] = cpu_to_le32(kdev_t_to_nr(inode->i_rdev));
>         else for (block = 0; block < EXT2_N_BLOCKS; block++)
>                 raw_inode->i_block[block] = inode->u.ext2_i.i_data[block];
> -       mark_buffer_dirty_inode(bh, inode);
> +       mark_buffer_dirty(bh);
>         if (do_sync) {
>                 ll_rw_block (WRITE, 1, &bh);
>                 wait_on_buffer (bh);

-- 

=====================================================================
Mohammad A. Haque                              http://www.haque.net/ 
                                               mhaque@haque.net

  "Alcohol and calculus don't mix.             Project Lead
   Don't drink and derive." --Unknown          http://wm.themes.org/
                                               batmanppc@themes.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/

  parent reply	other threads:[~2000-12-05  3:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-04  2:29 test12-pre4 Linus Torvalds
2000-12-04  3:57 ` test12-pre4 Mohammad A. Haque
2000-12-04  8:03   ` test12-pre4 Jeff Garzik
2000-12-04 12:25     ` test12-pre4 Alan Cox
2000-12-04 12:21   ` test12-pre4 Alan Cox
2000-12-04 20:22     ` test12-pre4 Nikhil Goel
2000-12-04  6:01 ` [PATCH] inode dirty blocks test12-pre4 Alexander Viro
2000-12-04 13:25   ` Andrew Morton
2000-12-04 13:49     ` [PATCH] inode dirty blocks Alexander Viro
2000-12-05  1:47       ` Andrew Morton
2000-12-05  2:41         ` Linus Torvalds
2000-12-05  3:31           ` Alexander Viro
2000-12-05  3:52             ` Linus Torvalds
2000-12-05  4:19               ` Alexander Viro
2000-12-05  2:49         ` Mohammad A. Haque [this message]
2000-12-05  4:15           ` Peter Samuelson
2000-12-04 18:16   ` [PATCH] inode dirty blocks Re: test12-pre4 Stephen C. Tweedie
2000-12-04 19:54     ` Alexander Viro
2000-12-05 20:35   ` Andrew Morton

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=3A2C57B2.57DA3BA6@haque.net \
    --to=mhaque@haque.net \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox