From: Bin Liu <b-liu@ti.com>
To: Colin King <colin.king@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: musb: fix indentation issue on a return statement
Date: Mon, 07 Jan 2019 20:21:34 +0000 [thread overview]
Message-ID: <20190107202134.GE25910@uda0271908> (raw)
In-Reply-To: <20190104175941.9669-1-colin.king@canonical.com>
Hi,
On Fri, Jan 04, 2019 at 05:59:41PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> A return statement is indented one level too far, fix this by removing
> a tab.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/usb/musb/musb_host.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied. Thanks.
Regards,
-Bin.
prev parent reply other threads:[~2019-01-07 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 17:59 [PATCH] USB: musb: fix indentation issue on a return statement Colin King
2019-01-07 20:21 ` Bin Liu [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=20190107202134.GE25910@uda0271908 \
--to=b-liu@ti.com \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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 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).