From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Samuel Ortiz <samuel@sortiz.org>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch net-next] irda: w83977af_ir: cleanup an indent issue
Date: Mon, 12 Dec 2016 15:22:08 +0000 [thread overview]
Message-ID: <1481556128.1764.17.camel@perches.com> (raw)
In-Reply-To: <20161212112134.GA10035@elgon.mountain>
On Mon, 2016-12-12 at 14:21 +0300, Dan Carpenter wrote:
> In commit 99d8d2159d7c ("irda: w83977af_ir: Neaten logging"), we
> accidentally added an extra tab to these lines.
Thanks Dan.
Oops, It's kinda funny I did the whole
series to fix that misindentation originally
and added it back when rebasing.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Samuel Ortiz <samuel@sortiz.org>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch net-next] irda: w83977af_ir: cleanup an indent issue
Date: Mon, 12 Dec 2016 07:22:08 -0800 [thread overview]
Message-ID: <1481556128.1764.17.camel@perches.com> (raw)
In-Reply-To: <20161212112134.GA10035@elgon.mountain>
On Mon, 2016-12-12 at 14:21 +0300, Dan Carpenter wrote:
> In commit 99d8d2159d7c ("irda: w83977af_ir: Neaten logging"), we
> accidentally added an extra tab to these lines.
Thanks Dan.
Oops, It's kinda funny I did the whole
series to fix that misindentation originally
and added it back when rebasing.
next prev parent reply other threads:[~2016-12-12 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 11:21 [patch net-next] irda: w83977af_ir: cleanup an indent issue Dan Carpenter
2016-12-12 11:21 ` Dan Carpenter
2016-12-12 15:22 ` Joe Perches [this message]
2016-12-12 15:22 ` Joe Perches
2016-12-18 2:33 ` David Miller
2016-12-18 2:33 ` David Miller
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=1481556128.1764.17.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.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.