All of lore.kernel.org
 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,
	hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cgroup: fix one typo in cgroup.c
Date: Mon, 24 Aug 2015 16:19:00 +0800	[thread overview]
Message-ID: <55DAD374.7090805@huawei.com> (raw)
In-Reply-To: <1439890489-29124-1-git-send-email-lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>

On 2015/8/18 17:34, Xiubo Li wrote:
> There is one typo in kernel/cgroup.c, and they may introduce some
> noise when checking new patches.
>

There's a patch that will remove this line, see

https://lkml.org/lkml/2015/8/11/623

> Signed-off-by: Xiubo Li <lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>
> ---
>   kernel/cgroup.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index f89d929..d0cd33e 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -1043,7 +1043,7 @@ static char *cgroup_file_name(struct cgroup *cgrp, const struct cftype *cft,
>    * returns cft->mode if ->mode is not 0
>    * returns S_IRUGO|S_IWUSR if it has both a read and a write handler
>    * returns S_IRUGO if it has only a read handler
> - * returns S_IWUSR if it has only a write hander
> + * returns S_IWUSR if it has only a write handler
>    */
>   static umode_t cgroup_file_mode(const struct cftype *cft)
>   {
>

      parent reply	other threads:[~2015-08-24  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:34 [PATCH] cgroup: fix one typo in cgroup.c Xiubo Li
     [not found] ` <1439890489-29124-1-git-send-email-lixiubo-0p4V/sDNsUmm0O/7XYngnFaTQe2KTcn/@public.gmane.org>
2015-08-24  8:19   ` Zefan Li [this message]

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=55DAD374.7090805@huawei.com \
    --to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=hannes-druUgvl0LCNAfugRpC6u6w@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 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.