From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Markus Elfring <Markus.Elfring@web.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Hannes Reinecke <hare@suse.de>,
Johannes Thumshirn <jth@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Naohiro Aota <Naohiro.Aota@wdc.com>
Subject: Re: [v10 1/2] fs: New zonefs file system
Date: Wed, 5 Feb 2020 07:46:07 +0000 [thread overview]
Message-ID: <BYAPR04MB5816A4CD15C760D0E5768285E7020@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: b1336be5-16f1-cb46-3469-46974406de14@web.de
On 2020/02/05 16:17, Markus Elfring wrote:
>> Declaring it as
>>
>> static const char * const zgroups_name[] = { "cnv", "seq" };
>>
>> is probably what you are suggesting,
>
> Yes.
>
>
>> but since the string literals are already constants by default,
>> I do not think there is any difference.
>
> I propose to define this array also as a completely immutable data structure.
I understood that and pointed out that the added "const" does not change a
thing. I think that as is, it already is immutable. But sure, I can add
that const, no problem.
>
> Regards,
> Markus
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-02-05 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 9:46 [PATCH v10 1/2] fs: New zonefs file system Markus Elfring
2020-02-05 1:35 ` Damien Le Moal
2020-02-05 7:16 ` [v10 " Markus Elfring
2020-02-05 7:46 ` Damien Le Moal [this message]
2020-02-05 10:44 ` Markus Elfring
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=BYAPR04MB5816A4CD15C760D0E5768285E7020@BYAPR04MB5816.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=Markus.Elfring@web.de \
--cc=Naohiro.Aota@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=hare@suse.de \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).