linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Gao Xiang <gaoxiang25@huawei.com>, Chao Yu <yuchao0@huawei.com>,
	linux-erofs@lists.ozlabs.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: erofs: use explicit unsigned int type
Date: Mon, 10 Sep 2018 10:10:27 +0200	[thread overview]
Message-ID: <20180910081027.GA31845@kroah.com> (raw)
In-Reply-To: <20180909183753.11021-1-linux@weissschuh.net>

On Sun, Sep 09, 2018 at 08:37:53PM +0200, Thomas Weißschuh wrote:
> Changes since v1:
> 
> * Removed changes that conflicted with
>   [PATCH 1/6] staging: erofs: formatting fix in unzip_vle_lz4.c
> * Added patch description
> 
> Changes since v2:
> 
> * Fixed conflicts with other patchsets
> * Don't introduce new style issues
> 

These changes belong below the --- line, not above it.  I'm not sure if
git will handle this line:

> -- >8 --

Correctly or not, have you tried it?

thanks,

greg k-h

  reply	other threads:[~2018-09-10  8:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180830205605.19492-1-linux@weissschuh.net>
2018-09-07 16:39 ` [PATCH v2] staging: erofs: use explicit unsigned int type Thomas Weißschuh
2018-09-08  3:28   ` Gao Xiang
2018-09-09 15:16     ` Chao Yu
2018-09-09 18:34     ` [PATCH] MAINTAINERS: add tree location for staging/erofs Thomas Weißschuh
2018-09-10  3:56       ` Gao Xiang
2018-09-10 15:59         ` Chao Yu
2018-09-10 16:50           ` Gao Xiang
2018-09-10 19:41           ` [PATCH v4] staging: erofs: use explicit unsigned int type Thomas Weißschuh
2018-09-11 16:46             ` Chao Yu
2018-09-12  6:21             ` Gao Xiang
2018-09-13 16:46               ` Gao Xiang
2018-09-09 18:37     ` [PATCH v3] " Thomas Weißschuh
2018-09-10  8:10       ` Greg Kroah-Hartman [this message]
2018-09-10 19:15         ` Thomas Weißschuh

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=20180910081027.GA31845@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gaoxiang25@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=yuchao0@huawei.com \
    /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).