From: gregkh@linuxfoundation.org (Greg KH)
Subject: [PATCH v3] staging: erofs: Add whitespace after declaration
Date: Mon, 18 Mar 2019 16:38:16 +0100 [thread overview]
Message-ID: <20190318153816.GA15943@kroah.com> (raw)
In-Reply-To: <20190318153224.GA3596@bharath12345-Inspiron-5559>
On Mon, Mar 18, 2019@09:02:24PM +0530, Bharath Vedartham wrote:
> Add whitespace after declaration. Fixed the checkpatch.pl warning.
>
> ---
No signed-off-by?
> changes since v2
> - mutt gave me a lot of problems. Hence 3 patches for a really
> small problem.
> - Fixed the extra missing line.
>
> Signed-off-by: Bharath Vedartham <linux.bhar at gmail.com>
It needs to be above the --- line, otherwise it will be stripped off
when applied.
v4 please?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: gaoxiang25@huawei.com, yuchao0@huawei.com,
devel@driverdev.osuosl.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: erofs: Add whitespace after declaration
Date: Mon, 18 Mar 2019 16:38:16 +0100 [thread overview]
Message-ID: <20190318153816.GA15943@kroah.com> (raw)
In-Reply-To: <20190318153224.GA3596@bharath12345-Inspiron-5559>
On Mon, Mar 18, 2019 at 09:02:24PM +0530, Bharath Vedartham wrote:
> Add whitespace after declaration. Fixed the checkpatch.pl warning.
>
> ---
No signed-off-by?
> changes since v2
> - mutt gave me a lot of problems. Hence 3 patches for a really
> small problem.
> - Fixed the extra missing line.
>
> Signed-off-by: Bharath Vedartham <linux.bhar@gmail.com>
It needs to be above the --- line, otherwise it will be stripped off
when applied.
v4 please?
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-18 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:32 [PATCH v3] staging: erofs: Add whitespace after declaration Bharath Vedartham
2019-03-18 15:32 ` Bharath Vedartham
2019-03-18 15:38 ` Greg KH [this message]
2019-03-18 15:38 ` Greg KH
2019-03-18 15:40 ` Gao Xiang
2019-03-18 15:40 ` Gao Xiang
2019-03-18 16:00 ` Bharath Vedartham
2019-03-18 16:00 ` Bharath Vedartham
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=20190318153816.GA15943@kroah.com \
--to=gregkh@linuxfoundation.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.