From: Joe Perches <joe@perches.com>
To: Maxim Zhukov <mussitantesmortem@gmail.com>, davem@davemloft.net
Cc: linux@rainbow-software.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style
Date: Wed, 23 Mar 2016 07:50:01 -0700 [thread overview]
Message-ID: <1458744601.6819.4.camel@perches.com> (raw)
In-Reply-To: <1458743800-30606-1-git-send-email-mussitantesmortem@gmail.com>
On Wed, 2016-03-23 at 17:36 +0300, Maxim Zhukov wrote:
> This commit fixed spacing errors and warnings.
This commit log should show that you've tested this
by stating something like:
"git diff -w shows no difference"
and
"objdiff shows no changes"
If objdiff shows changes, you need to be show
why it's OK.
next prev parent reply other threads:[~2016-03-23 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 14:36 [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style Maxim Zhukov
2016-03-23 14:36 ` [PATCH 2/2] drivers: net: ethernet: dlink: dl2k: fix indent Maxim Zhukov
2016-03-23 14:50 ` Joe Perches [this message]
2016-03-23 17:41 ` [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-03-23 15:57 Maxim Zhukov
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=1458744601.6819.4.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=mussitantesmortem@gmail.com \
--cc=netdev@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).