From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [ANN] Squashfs 3.3 released
Date: Wed, 07 Nov 2007 16:06:10 +0000 [thread overview]
Message-ID: <4731E272.7050700@lougher.demon.co.uk> (raw)
In-Reply-To: <472FA4F7.4090705@msgid.tls.msk.ru>
Michael Tokarev wrote:
>
> A tiny bug[fix] I always forgot to send... In fs/squashfs/inode.c,
> constants TASK_UNINTERRUPTIBLE and TASK_INTERRUPTIBLE are used, but
> they aren't sometimes defined (declared in linux/sched.h):
>
Thanks - Squashfs gained a lot of #includes over time, many which I deemed were
unnecessary and removed in Squashfs 3.2. I obviously removed too many.
Fix applied to CVS.
Phillip
prev parent reply other threads:[~2007-11-07 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 11:13 [ANN] Squashfs 3.3 released Phillip Lougher
2007-11-05 11:56 ` maximilian attems
2007-11-07 16:32 ` Phillip Lougher
2007-11-20 23:50 ` Dave Jones
2007-11-21 14:02 ` Phillip Lougher
2007-11-21 14:48 ` Christoph Hellwig
2007-11-21 15:00 ` Phillip Lougher
2007-11-05 23:19 ` Michael Tokarev
2007-11-07 16:06 ` 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=4731E272.7050700@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).