From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: linux-next: manual merge of the trivial tree with the ext4 tree
Date: Fri, 31 Dec 2010 17:15:12 +0100 [thread overview]
Message-ID: <20101231161512.GG14221@pengutronix.de> (raw)
In-Reply-To: <20101231125721.3c3f4604.sfr@canb.auug.org.au>
Hi Stephen,
On Fri, Dec 31, 2010 at 12:57:21PM +1100, Stephen Rothwell wrote:
> diff --cc fs/ext4/ext4.h
> index 2a73925,1f253a9..0000000
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@@ -561,7 -561,23 +561,7 @@@ struct ext4_new_group_data
> #define EXT4_IOC32_SETVERSION_OLD FS_IOC32_SETVERSION
> #endif
>
> - /* Max physical block we can addres w/o extents */
> -
> -/*
> - * Mount options
> - */
> -struct ext4_mount_options {
> - unsigned long s_mount_opt;
> - uid_t s_resuid;
> - gid_t s_resgid;
> - unsigned long s_commit_interval;
> - u32 s_min_batch_time, s_max_batch_time;
> -#ifdef CONFIG_QUOTA
> - int s_jquota_fmt;
> - char *s_qf_names[MAXQUOTAS];
> -#endif
> -};
> -
> + /* Max physical block we can address w/o extents */
> #define EXT4_MAX_BLOCK_FILE_PHYS 0xFFFFFFFF
>
> /*
>
Looks correct.
Independant of this I think it would be better to define
EXT4_MAX_BLOCK_FILE_PHYS to 0xFFFFFFFFUL to have the same type on all
platforms.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-12-31 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 1:57 linux-next: manual merge of the trivial tree with the ext4 tree Stephen Rothwell
2010-12-31 16:15 ` Uwe Kleine-König [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-25 7:34 Stephen Rothwell
2009-11-25 11:16 ` Jiri Kosina
2009-11-25 11:45 ` tytso
2009-11-25 11:56 ` Jiri Kosina
2009-11-25 12:25 ` Stephen Rothwell
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=20101231161512.GG14221@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.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 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.