From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Dave Kleikamp <shaggy@austin.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [RFC:PATCH 000/002] EXT3: cleanups in preparation for ext4 clone
Date: Fri, 8 Sep 2006 17:39:17 -0400 [thread overview]
Message-ID: <20060908213914.11498.3272.sendpatchset@kleikamp.austin.ibm.com> (raw)
I'm working on rebasing Mingming's ext4 patches on the -mm tree, and have
noticed a couple cleanups that would be nice to have in ext3 before the
code diverges.
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next reply other threads:[~2006-09-08 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 21:39 Dave Kleikamp [this message]
2006-09-08 21:39 ` [RFC:PATCH 001/002] EXT3: More whitespace cleanups Dave Kleikamp
2006-09-08 21:39 ` [RFC:PATCH 002/002] EXT3: Fix sparse warnings Dave Kleikamp
2006-09-08 22:17 ` Alexey Dobriyan
2006-09-10 14:31 ` Dave Kleikamp
2006-09-08 21:56 ` [RFC:PATCH 000/002] EXT3: cleanups in preparation for ext4 clone Andrew Morton
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=20060908213914.11498.3272.sendpatchset@kleikamp.austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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