Linux cgroups development
 help / color / mirror / Atom feed
From: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Xiubo Li
	<lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>,
	tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cgroup: fix written mistake in warning message
Date: Fri, 26 Feb 2016 12:16:12 +0800	[thread overview]
Message-ID: <56CFD18C.30305@huawei.com> (raw)
In-Reply-To: <1456454528-10269-1-git-send-email-lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>

On 2016/2/26 10:42, Xiubo Li wrote:
> There is written mistake about the print format name:id <--> %d:%s,
> which the name is 'char *' type and id is 'int' type.
> 
> Signed-off-by: Xiubo Li <lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>

Good catch. :)

but could instead change "name:id" to "id:name"? so it's consistent with
"cgroup_subsys %d:%s".

> ---
>  kernel/cgroup.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index cc40463..0f82d16 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -5324,9 +5324,9 @@ int __init cgroup_init_early(void)
>  
>  	for_each_subsys(ss, i) {
>  		WARN(!ss->css_alloc || !ss->css_free || ss->name || ss->id,
> -		     "invalid cgroup_subsys %d:%s css_alloc=%p css_free=%p name:id=%d:%s\n",
> +		     "invalid cgroup_subsys %d:%s css_alloc=%p css_free=%p name:id=%s:%d\n",
>  		     i, cgroup_subsys_name[i], ss->css_alloc, ss->css_free,
> -		     ss->id, ss->name);
> +		     ss->name, ss->id);
>  		WARN(strlen(cgroup_subsys_name[i]) > MAX_CGROUP_TYPE_NAMELEN,
>  		     "cgroup_subsys_name %s too long\n", cgroup_subsys_name[i]);
>  
> 

  parent reply	other threads:[~2016-02-26  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  2:42 [PATCH] cgroup: fix written mistake in warning message Xiubo Li
     [not found] ` <1456454528-10269-1-git-send-email-lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>
2016-02-26  4:16   ` Zefan Li [this message]
     [not found]     ` <56CFD18C.30305-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-02-26  4:59       ` Xiubo Li

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=56CFD18C.30305@huawei.com \
    --to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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