From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>
Subject: Re: [PATCH 2/3] cgroup: add cgroup_name() API
Date: Mon, 4 Mar 2013 11:02:37 +0800 [thread overview]
Message-ID: <51340ECD.1030905@huawei.com> (raw)
In-Reply-To: <CAOS58YPNAPhWUwNq9G39Airo+TvV2ecXBiNU5s9PFqkL3RbRFg@mail.gmail.com>
On 2013/3/2 4:45, Tejun Heo wrote:
> Hello, Al.
>
> On Fri, Mar 1, 2013 at 12:39 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>>>> Flexible array members can be statically initialized. If you wanna be
>>>> really anal about it, you can do it manually with a wrapping struct
>>>> but I don't think that would be necessary.
>>>>
>>>
>>> I didn't know this difference between flexible array and zero-size array.
>>> Thanks.
>>
>> Mind you, initializing flex array member is explicitly invalid per C99;
>> it's a GNU extension...
>
> Yeah, that's what I meant by the "anal" part although it seems like
> c99 doesn't even allow that. Do we care tho? It seems like a logical
> feature which should show up in the standard eventually. Maybe it
> could be a problem for clang?
>
Do we have a decision now? Please pick v4 if this GNU extension can't be used
in kernel code, otherwise v5.
next prev parent reply other threads:[~2013-03-04 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 6:17 [PATCH v3 1/3] cgroup: fix cgroup_path() vs rename() race Li Zefan
2013-02-25 6:17 ` [PATCH 2/3] cgroup: add cgroup_name() API Li Zefan
2013-02-26 2:27 ` Tejun Heo
2013-02-26 10:25 ` Li Zefan
2013-02-26 13:26 ` Tejun Heo
2013-02-27 10:49 ` Li Zefan
2013-02-27 13:23 ` Tejun Heo
2013-02-28 6:53 ` Li Zefan
2013-02-28 14:49 ` Tejun Heo
2013-03-01 6:36 ` Li Zefan
2013-03-01 20:39 ` Al Viro
2013-03-01 20:45 ` Tejun Heo
2013-03-04 3:02 ` Li Zefan [this message]
2013-03-04 17:38 ` Tejun Heo
2013-02-25 6:18 ` [PATCH 3/3] cpuset: use cgroup_name() in cpuset_print_task_mems_allowed() Li Zefan
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=51340ECD.1030905@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.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 NNTP newsgroup(s).