From: marcin.slusarz@gmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ben Fennema <bfennema@falcon.csc.calpoly.edu>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Marcin Slusarz <marcin.slusarz@gmail.com>
Subject: [PATCH 0/6] udf: improve code related to super_block v3
Date: Sun, 6 Jan 2008 01:44:29 +0100 [thread overview]
Message-ID: <1199580275-2487-1-git-send-email-marcin.slusarz@gmail.com> (raw)
Hi
This patchset converts macros related to super_block into
functions. Besides that it fixes some sparse warnings (6th),
improves coding style (1st) and fixes error handling (4th).
Note that udf files has really long lines and these patches won't
validate by checkpatch. Next patchset will clean it up almost completely.
(Only 3rd patch changed from second version)
Second version: http://lkml.org/lkml/2007/12/23/197
First version: http://lkml.org/lkml/2007/12/22/150
Marcin Slusarz
next reply other threads:[~2008-01-06 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 0:44 marcin.slusarz [this message]
2008-01-06 0:44 ` [PATCH] udf: fix coding style of super.c marcin.slusarz
2008-01-07 13:33 ` Jan Kara
2008-01-06 0:44 ` [PATCH] udf: remove some ugly macros marcin.slusarz
2008-01-06 0:44 ` [PATCH] udf: convert UDF_SB_ALLOC_PARTMAPS macro to udf_sb_alloc_partition_maps function marcin.slusarz
2008-01-06 0:44 ` [PATCH] udf: check if udf_load_logicalvol failed marcin.slusarz
2008-01-07 12:19 ` Christoph Hellwig
2008-01-06 0:44 ` [PATCH] udf: convert some macros to functions marcin.slusarz
2008-01-07 12:26 ` Christoph Hellwig
2008-01-07 20:44 ` Marcin Slusarz
2008-01-07 23:28 ` Andrew Morton
2008-01-08 6:52 ` Marcin Slusarz
2008-01-08 10:09 ` Jan Kara
2008-01-06 0:44 ` [PATCH] udf: fix sparse warnings (shadowing & mismatch between declaration and definition) marcin.slusarz
2008-01-07 12:26 ` Christoph Hellwig
2008-01-06 0:52 ` [PATCH 0/6] udf: improve code related to super_block v3 Marcin Slusarz
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=1199580275-2487-1-git-send-email-marcin.slusarz@gmail.com \
--to=marcin.slusarz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--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
all inboxes | Powered by JetHome®