linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian McMenamin <adrian@newgolddream.dyndns.info>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-sh <linux-sh@vger.kernel.org>
Subject: Re: [RFC][patch] filesystem: Vmufat filesystem, version 4
Date: Tue, 14 Apr 2009 09:38:50 +0200	[thread overview]
Message-ID: <20090414073850.GA11577@uranus.ravnborg.org> (raw)
In-Reply-To: <1239654768.6542.10.camel@localhost.localdomain>

Hi Adrian.

I see that most of the point raised in last round has been addressed.
An incremental changelog would be nice during this RFC phase
so we know what has been changed from one version to the next.

> +/*
> + * write out the date in bcd format
> + * in the appropriate part of the 
> + * directory entry
> + */
> +static unsigned long vmufat_save_bcd(char *bh, int z)
> +{
> +	unsigned char day, year, century, nl_day, month;
> +	unsigned char u8year;
> +	unsigned long unix_date = CURRENT_TIME.tv_sec;
> +
> +	day = unix_date / 86400 - 3652;
> +	year = day / 365;
> +
> +	if ((year + 3) / 4 + 365 * year > day)
> +		year--;
> +
> +	day -= (year + 3) / 4 + 365 * year;
> +	if (day == 59 && !(year & 3)) {
> +		nl_day = day;
> +		month = 2;
> +	} else {
> +		nl_day = (year & 3) || day <= 59 ? day : day - 1;
> +		for (month = 0; month < 12; month++)
> +			if (day_n[month] > nl_day)
> +				break;
> +	}
> +
> +	century = 19;
> +	if (year > 19)
> +		century = 20;
> +
> +	bh[z + 0x10] = bin2bcd(century);
> +	u8year = year + 80;
> +	if (u8year > 99)
> +		u8year = u8year - 100;
> +
> +	bh[z + 0x11] = bin2bcd(u8year);
> +	bh[z + 0x12] = bin2bcd(month);
> +	bh[z + 0x13] =
> +	    bin2bcd(day - day_n[month - 1] + 1);
> +	bh[z + 0x14] =
> +	    bin2bcd((unix_date / 3600) % 24);
> +	bh[z + 0x15] = bin2bcd((unix_date / 60) % 60);
> +	bh[z + 0x16] = bin2bcd(unix_date % 60);
> +	return unix_date;
> +}

Can we get all these numbers replaced by a set of descriptive constants?
You can then use the definition of the constants to more-or-less document
the on-disk format.

You have it in several places - the above is just one of them.

I did not look into the rest of the filesystem this time,
I may do so later.

Please ntoe that this part of the excercise is to make the filesystem
ready to be reviewed by someone who knows how to write a filesystem.
What I provide to you is only the janitorial level..

	Sam

  parent reply	other threads:[~2009-04-14  7:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 20:32 [RFC][patch] filesystem: Vmufat filesystem, version 4 Adrian McMenamin
2009-04-13 21:00 ` Paul Mundt
2009-04-13 21:36   ` Adrian McMenamin
2009-04-13 21:40     ` Adrian McMenamin
2009-04-13 22:28       ` Mike Frysinger
2009-04-13 21:59     ` Paul Mundt
2009-04-14  7:00       ` Adrian McMenamin
2009-04-14  7:03         ` Paul Mundt
2009-04-14  7:16           ` Adrian McMenamin
2009-04-14  7:23             ` Mike Frysinger
2009-04-14  7:38 ` Sam Ravnborg [this message]
2009-04-16 11:23 ` Al Viro
2009-04-24 22:14 ` Pavel Machek
2009-04-27 17:56   ` Mike Frysinger
2009-04-27 18:03     ` Pavel Machek

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=20090414073850.GA11577@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=adrian@newgolddream.dyndns.info \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@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).