From: Jiri Slaby <jirislaby@gmail.com>
To: "Daniel Aragonés" <danarag@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] Requested changelog for minix filesystem update to V3
Date: Mon, 01 May 2006 13:59:10 +0159 [thread overview]
Message-ID: <4455F825.2060802@gmail.com> (raw)
In-Reply-To: <4455D3F1.7000102@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Aragonés napsal(a):
> Hi Andrew,
>
> Thank you for your interest. The file attached now has been diffed
> against last week's 2.6.16.11.
>
> Changelog:
>
> In bitmap.c, the access to architecture dependent functions has been
> kept within the range of 1K blocksize. A loop inside a loop has been
> introduced to do so.
> In inode.c, 'sbi->s_ninodes = m3s->s_ninodes' was missing, and variable
> 'block' is now unsigned.
> In itree_common.c, function 'nblocks(loff_t size)' has been modified to
> fix the shift in 'blocks = (size + BLOCK_SIZE - 1) >> BLOCK_SIZE_BITS'.
> In minix.h, minor and cosmetic corrections.
>
> Regards.
>
> Signed-off-by: Daniel Aragones <danarag@gmail.com>
>
>
> ------------------------------------------------------------------------
>
[snip]
> diff -ur orig.Linux-2.6.16.11/fs/minix/dir.c updated.Linux-2.6.16.11/fs/minix/dir.c
> --- orig.Linux-2.6.16.11/fs/minix/dir.c 2006-04-24 22:20:24.000000000 +0200
> +++ updated.Linux-2.6.16.11/fs/minix/dir.c 2006-03-28 18:04:28.000000000 +0200
> @@ -4,12 +4,15 @@
> * Copyright (C) 1991, 1992 Linus Torvalds
> *
> * minix directory handling functions
> + *
> + * Updated to filesystem version 3 by Daniel Aragones
> */
>
> #include "minix.h"
> #include <linux/highmem.h>
> #include <linux/smp_lock.h>
>
> +typedef struct minix3_dir_entry minix3_dirent;
> typedef struct minix_dir_entry minix_dirent;
are typedefs _really_ needed? I think we want to kill them all.
regards,
- --
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEVfglMsxVwznUen4RAmKwAJ91Zj8O2Wz+EFp1GPcVe1ytwbgVCACfRIEQ
PRBY5/PEQKXbjQVJnSPmRnU=
=jBAY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-01 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 9:25 Daniel Aragonés
2006-05-01 9:34 ` Andrew Morton
2006-05-01 9:34 ` Pekka Enberg
2006-05-01 12:00 ` Jiri Slaby [this message]
2006-05-01 13:06 ` Jesper Juhl
2006-05-01 13:43 ` Willy Tarreau
2006-05-01 14:21 ` Jesper Juhl
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=4455F825.2060802@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=danarag@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®