From: Phillip Lougher <phillip.lougher@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nick Terrell <terrelln@fb.com>,
"Austin S . Hemmelgarn" <ahferroin7@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
kernel-team@fb.com, Chris Mason <clm@fb.com>,
Yann Collet <cyan@fb.com>, Adam Borowski <kilobyte@angband.pl>,
David Sterba <dsterba@suse.cz>,
SquashFS developers <squashfs-devel@lists.sourceforge.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Phillip Lougher <phillip@squashfs.org.uk>,
Sean Purcell <me@seanp.xyz>
Subject: Re: [PATCH v4 4/5] squashfs: Add zstd support
Date: Mon, 14 Aug 2017 03:23:28 +0100 [thread overview]
Message-ID: <CAB3wodfARQsBPb2Cw97AmjsTwTXBdeRmsbs+uajt4idhXAf=QA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdXGR2zG+LS9Qa1foLfWCzpFSmq2f=mNJp-65bH3ZwjoAA@mail.gmail.com>
On Sun, Aug 13, 2017 at 9:31 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Fri, Aug 4, 2017 at 10:19 PM, Nick Terrell <terrelln@fb.com> wrote:
>> --- a/fs/squashfs/decompressor.c
>> +++ b/fs/squashfs/decompressor.c
>> @@ -65,6 +65,12 @@ static const struct squashfs_decompressor squashfs_zlib_comp_ops = {
>> };
>> #endif
>>
>> +#ifndef CONFIG_SQUASHFS_ZSTD
>> +static const struct squashfs_decompressor squashfs_zstd_comp_ops = {
>> + NULL, NULL, NULL, NULL, ZSTD_COMPRESSION, "zstd", 0
>
> Can you please use designated initializers?
I prefer it as it is. It matches the coding style that I used in the
rest of that file to declare the "unsupported" compressor entries (if
this patch uses a different style it would look odd). There's no
pointers to functions being assigned here, and it makes it a short and
concise one-line.
Phillip
>
>> +};
>> +#endif
>> +
>> static const struct squashfs_decompressor squashfs_unknown_comp_ops = {
>> NULL, NULL, NULL, NULL, 0, "unknown", 0
>> ;
>
>> +const struct squashfs_decompressor squashfs_zstd_comp_ops = {
>> + .init = zstd_init,
>> + .free = zstd_free,
>> + .decompress = zstd_uncompress,
>> + .id = ZSTD_COMPRESSION,
>> + .name = "zstd",
>> + .supported = 1
>> +};
>
> ... like you did here.
>
> 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:[~2017-08-14 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 20:19 [PATCH v4 0/5] Add xxhash and zstd modules Nick Terrell
2017-08-04 20:19 ` [PATCH v4 1/5] lib: Add xxhash module Nick Terrell
2017-08-04 20:19 ` [PATCH v4 3/5] btrfs: Add zstd support Nick Terrell
2017-08-04 20:19 ` [PATCH v4 4/5] squashfs: " Nick Terrell
2017-08-04 22:10 ` Linus Torvalds
2017-08-04 22:32 ` Nick Terrell
2017-08-04 23:39 ` Sean Purcell
2017-08-13 8:31 ` Geert Uytterhoeven
2017-08-14 2:23 ` Phillip Lougher [this message]
2017-08-04 20:19 ` [PATCH v4 5/5] crypto: " Nick Terrell
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='CAB3wodfARQsBPb2Cw97AmjsTwTXBdeRmsbs+uajt4idhXAf=QA@mail.gmail.com' \
--to=phillip.lougher@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=cyan@fb.com \
--cc=dsterba@suse.cz \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-team@fb.com \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@seanp.xyz \
--cc=phillip@squashfs.org.uk \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=terrelln@fb.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;
as well as URLs for NNTP newsgroup(s).