From: David Miller <davem@davemloft.net>
To: eladkan@mellanox.com
Cc: linux-kernel@vger.kernel.org, abrodkin@synopsys.com,
netdev@vger.kernel.org, noamca@mellanox.com
Subject: Re: [PATCH 0/2] Code style fixes
Date: Wed, 13 Jul 2016 20:59:25 -0700 (PDT) [thread overview]
Message-ID: <20160713.205925.1493231800901383619.davem@davemloft.net> (raw)
In-Reply-To: <1468418287-26512-1-git-send-email-eladkan@mellanox.com>
From: Elad Kanfi <eladkan@mellanox.com>
Date: Wed, 13 Jul 2016 16:58:05 +0300
> Fix all checkpatch warnings and errors, and reuse code
Series applied to net-next, thanks.
prev parent reply other threads:[~2016-07-14 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 13:58 [PATCH 0/2] Code style fixes Elad Kanfi
2016-07-13 13:58 ` [PATCH 1/2] net: nps_enet: fix coding style issues Elad Kanfi
2016-07-13 13:58 ` [PATCH 2/2] net: nps_enet: code reuse Elad Kanfi
2016-07-14 3:59 ` David Miller [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=20160713.205925.1493231800901383619.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=abrodkin@synopsys.com \
--cc=eladkan@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noamca@mellanox.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).