All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Vladimir Zapolskiy <vladimir@tuxera.com>,
	Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org,
	Anton Altaparmakov <anton@tuxera.com>
Subject: Re: [PATCH] erofs: correct indentation of an assigned structure inside a function
Date: Thu, 2 Jan 2020 20:33:35 +0800	[thread overview]
Message-ID: <09a203da-1f08-3ea0-e457-dfb1d251e08c@huawei.com> (raw)
In-Reply-To: <20200102120232.15074-1-vladimir@tuxera.com>

On 2020/1/2 20:02, Vladimir Zapolskiy wrote:
> Trivial change, the expected indentation ruled by the coding style
> hasn't been met.
> 
> Signed-off-by: Vladimir Zapolskiy <vladimir@tuxera.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <yuchao0@huawei.com>
To: Vladimir Zapolskiy <vladimir@tuxera.com>,
	Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-erofs@lists.ozlabs.org>,
	"Anton Altaparmakov" <anton@tuxera.com>
Subject: Re: [PATCH] erofs: correct indentation of an assigned structure inside a function
Date: Thu, 2 Jan 2020 20:33:35 +0800	[thread overview]
Message-ID: <09a203da-1f08-3ea0-e457-dfb1d251e08c@huawei.com> (raw)
In-Reply-To: <20200102120232.15074-1-vladimir@tuxera.com>

On 2020/1/2 20:02, Vladimir Zapolskiy wrote:
> Trivial change, the expected indentation ruled by the coding style
> hasn't been met.
> 
> Signed-off-by: Vladimir Zapolskiy <vladimir@tuxera.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

  parent reply	other threads:[~2020-01-02 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 12:02 [PATCH] erofs: correct indentation of an assigned structure inside a function Vladimir Zapolskiy
2020-01-02 12:02 ` Vladimir Zapolskiy
2020-01-02 12:25 ` Gao Xiang
2020-01-02 12:25   ` Gao Xiang
2020-01-02 12:33 ` Chao Yu [this message]
2020-01-02 12:33   ` Chao Yu

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=09a203da-1f08-3ea0-e457-dfb1d251e08c@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=anton@tuxera.com \
    --cc=chao@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=vladimir@tuxera.com \
    --cc=xiang@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.