From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Linux Embedded Maillist <linux-embedded@vger.kernel.org>,
Lasse Collin <lasse.collin@tukaani.org>,
Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH 2/2] Squashfs: Add XZ compression configuration option
Date: Sun, 16 Jan 2011 19:56:26 +0100 [thread overview]
Message-ID: <AANLkTinfFk-mkzgt_qw2+Y5GxkuPVC9S63reuG=GQ84=@mail.gmail.com> (raw)
In-Reply-To: <4D01C770.1080301@lougher.demon.co.uk>
On Fri, Dec 10, 2010 at 07:23, Phillip Lougher
<phillip@lougher.demon.co.uk> wrote:
> Geert Uytterhoeven wrote:
>> On Thu, Dec 9, 2010 at 07:11, Phillip Lougher
>> <phillip@lougher.demon.co.uk> wrote:
>>>
>>> --- a/fs/squashfs/Kconfig
>>> +++ b/fs/squashfs/Kconfig
>>> @@ -53,6 +53,22 @@ config SQUASHFS_LZO
>>>
>>> If unsure, say N.
>>>
>>> +config SQUASHFS_XZ
>>> + bool "Include support for XZ compressed file systems"
>>> + depends on SQUASHFS
>>> + default n
>>
>> "default n" is the default, no reason to specify it.
>>
>
> Yes, thanks for pointing that out.
>
> It seems there's a lot of "default n"s in the mainline kernel
>
> % find . -name "Kconfig"| xargs grep "default n" | wc
> 485 1535 18753
>
> including two in arch/m68k ;-)
Thanks, fixed.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2011-01-16 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 6:11 [PATCH 2/2] Squashfs: Add XZ compression configuration option Phillip Lougher
2010-12-09 7:02 ` Geert Uytterhoeven
2010-12-10 6:23 ` Phillip Lougher
2011-01-16 18:56 ` Geert Uytterhoeven [this message]
2010-12-09 9:09 ` Lasse Collin
2010-12-10 7:30 ` Phillip Lougher
2010-12-10 10:37 ` Lasse Collin
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='AANLkTinfFk-mkzgt_qw2+Y5GxkuPVC9S63reuG=GQ84=@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=apw@canonical.com \
--cc=lasse.collin@tukaani.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).