From: Artem Bityutskiy <dedekind1@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH v2 1/7] affs: stop setting bm_flags
Date: Wed, 27 Jun 2012 12:18:59 +0300 [thread overview]
Message-ID: <1340788739.29342.5.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAMuHMdXW80+jyp3te+uG+=kE5sCs=wRgKzE4CXAZVe3xGdFpmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On Sat, 2012-06-16 at 20:49 +0200, Geert Uytterhoeven wrote:
> > I could not find good documentation describing this field, except of one random
> > piece of documentation in the internet which says that -1 means that the root
> > block is valid, which is not consistent with what we have in the Linux AFFS
> > driver.
>
> The book "Amiga Intern" (German version on the 'net, which is faster to access
> than the Dutch version somewhere in my attic ;-) agrees with this ("Dieses Flag
> enthält -1 (TRUE), wenn die Bit-Map der Diskette gültig ist").
Thangs Geert for confirming.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-27 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 15:56 [PATCH v2 0/7] affs: stop using write_supers and s_dirt Artem Bityutskiy
2012-06-06 15:56 ` [PATCH v2 1/7] affs: stop setting bm_flags Artem Bityutskiy
2012-06-16 18:49 ` Geert Uytterhoeven
2012-06-27 9:18 ` Artem Bityutskiy [this message]
2012-06-06 15:56 ` [PATCH v2 2/7] affs: remove useless superblock writeout on unmount Artem Bityutskiy
2012-06-06 15:56 ` [PATCH v2 3/7] affs: remove useless superblock writeout on remount Artem Bityutskiy
2012-06-06 15:56 ` [PATCH v2 4/7] affs: re-structure superblock locking a bit Artem Bityutskiy
2012-06-06 15:56 ` [PATCH v2 5/7] affs: stop using lock_super Artem Bityutskiy
2012-06-06 15:56 ` [PATCH v2 6/7] affs: introduce VFS superblock object back-reference Artem Bityutskiy
2012-06-06 15:56 ` [PATCH v2 7/7] affs: get rid of affs_sync_super Artem Bityutskiy
2012-07-02 14:06 ` Artem Bityutskiy
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=1340788739.29342.5.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).