From: Andrew Morton <akpm@linux-foundation.org>
To: Warren Turkal <wt@penguintechs.org>
Cc: linux-fsdevel@vger.kernel.org, zippel@linux-m68k.org,
wt@penguintechs.org
Subject: Re: hfsplus journal detection - try 4
Date: Wed, 19 Nov 2008 14:49:16 -0800 [thread overview]
Message-ID: <20081119144916.28296257.akpm@linux-foundation.org> (raw)
In-Reply-To: <1226437008-14247-1-git-send-email-wt@penguintechs.org>
On Tue, 11 Nov 2008 12:56:45 -0800
Warren Turkal <wt@penguintechs.org> wrote:
> Here's another shot at this patch. I found a small issue with sparse.
> If this is suitable for inclusion, could someone please pull it into
> their tree so that it can be merged upstream?
I don't follow linux-fsdevel much. cc'ing linux-kernel gets my attention.
This patchset is missing an overall description of the problem which is
being solved. I can kinda see what the changes do, but it would be
much better if we were provided with a description of the kernel
behaviour before and after the patches.
prev parent reply other threads:[~2008-11-19 22:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:56 hfsplus journal detection - try 4 Warren Turkal
2008-11-11 20:56 ` [PATCH] Identify journal info block in volume header Warren Turkal
2008-11-11 20:56 ` [PATCH] Fix journal detection on HFS+ Warren Turkal
2008-11-11 20:56 ` [PATCH] Fix header include Warren Turkal
2008-11-19 22:51 ` Andrew Morton
2008-11-19 23:01 ` Brad Boyer
2008-11-20 0:41 ` Brad Boyer
2008-11-20 2:30 ` Warren Turkal
2008-11-19 22:51 ` [PATCH] Fix journal detection on HFS+ Andrew Morton
2008-11-20 1:01 ` Warren Turkal
2008-11-19 22:49 ` [PATCH] Identify journal info block in volume header Andrew Morton
2008-11-19 7:07 ` hfsplus journal detection - try 4 Warren Turkal
2008-11-19 8:39 ` Jörn Engel
2008-11-19 22:36 ` Warren Turkal
2008-11-19 22:49 ` Andrew Morton [this message]
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=20081119144916.28296257.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wt@penguintechs.org \
--cc=zippel@linux-m68k.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 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.