From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: akpm@linux-foundation.org, linux-embedded@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
tim.bird@am.sony.com
Subject: Re: Subject: [PATCH 12/16] Squashfs: header files
Date: Thu, 23 Oct 2008 09:56:21 +0100 [thread overview]
Message-ID: <49003C35.1090301@lougher.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0810221801570.5634@vixen.sonytel.be>
Geert Uytterhoeven wrote:
> On Fri, 17 Oct 2008, Phillip Lougher wrote:
>> +#ifdef SQUASHFS_TRACE
>> +#define TRACE(s, args...) printk(KERN_NOTICE "SQUASHFS: "s, ## args)
>> +#else
>> +#define TRACE(s, args...) {}
>> +#endif
>
> Just use
>
> #define TRACE(s, args...) pr_debug("SQUASHFS: "s, ## args)
OK.
>> +
>> +#define WARNING(s, args...) printk(KERN_WARNING "SQUASHFS: "s, ## args)
> ^^^^^^^^^^^^^^^^
> pr_warning(
>
OK.
>
> SQUASHFS_MKFLAGS() isn't used by the kernel, only by the tools (mksquashfs)?
>
Only used by mksquashfs. I pulled out the user-space only stuff into a
separate include, but must have missed this one.
>> +/* meta index cache */
>> +#define SQUASHFS_META_INDEXES (SQUASHFS_METADATA_SIZE / sizeof(unsigned int))
> ^^^^^^^^^^^^
> I was wondering whether a meta index is an `unsigned int' or an `__le32', but I
> couldn't find it easily.
>
Unsigned int, it's used internally by the index cache code (file.c). It
works out how many block indexes can fit into one compressed metadata block.
Phillip
prev parent reply other threads:[~2008-10-23 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:42 Subject: [PATCH 12/16] Squashfs: header files Phillip Lougher
2008-10-21 16:25 ` David P. Quigley
2008-10-21 18:17 ` Phillip Lougher
2008-10-22 16:13 ` Geert Uytterhoeven
2008-10-23 8:56 ` Phillip Lougher [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=49003C35.1090301@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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