From: Andreas Ziegler <andreas.ziegler@fau.de>
To: "Rosen, Rami" <rami.rosen@intel.com>, Tejun Heo <tj@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cgroup: Fix misspelling of CONFIG_SOCK_CGROUP_DATA in comments
Date: Tue, 26 Jan 2016 16:14:30 +0100 [thread overview]
Message-ID: <56A78D56.2030902@fau.de> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F92CB53E91@HASMSX110.ger.corp.intel.com>
On 01/26/2016 16:08, Rosen, Rami wrote:
> Hi,
>
> --- a/include/linux/cgroup.h
> +++ b/include/linux/cgroup.h
> @@ -604,11 +604,11 @@ static inline struct cgroup *sock_cgroup_ptr(struct sock_cgroup_data *skcd)
> #endif
> }
>
> In this occasion, seems that maybe something else is also missing:
> Shouldn't it be hereafter : +#else /* !CONFIG_SOCK_CGROUP_DATA */
> instead ?
>
> -#else /* CONFIG_CGROUP_DATA */
> +#else /* CONFIG_SOCK_CGROUP_DATA */
It seems that there is no real consensus among the developers for that
particular case:
ziegler@box:~/linux$ git grep "#else \/\* \!CONFIG_" | wc -l
327
ziegler@box:~/linux$ git grep "#else \/\* CONFIG_" | wc -l
564
I don't mind changing it, I'm just not sure if that's what we want.
Regards,
Andreas
next prev parent reply other threads:[~2016-01-26 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 14:39 [PATCH] cgroup: Fix misspelling of CONFIG_SOCK_CGROUP_DATA in comments Andreas Ziegler
[not found] ` <1453819158-25380-1-git-send-email-andreas.ziegler-d40JDW7QUjc@public.gmane.org>
2016-01-26 15:08 ` Rosen, Rami
2016-01-26 15:08 ` Rosen, Rami
2016-01-26 15:14 ` Andreas Ziegler [this message]
[not found] ` <56A78D56.2030902-d40JDW7QUjc@public.gmane.org>
2016-01-26 15:34 ` Johannes Weiner
2016-01-26 15:34 ` Johannes Weiner
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=56A78D56.2030902@fau.de \
--to=andreas.ziegler@fau.de \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rami.rosen@intel.com \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.