From: Krzysztof Majzerowicz-Jaszcz <cristos@vipserv.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Joe Perches <joe@perches.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drivers: net: ethernet: intel: e1000: e1000_ethertoo.c coding style fixes
Date: Tue, 19 Aug 2014 19:33:56 +0200 [thread overview]
Message-ID: <53F38A84.3070702@vipserv.org> (raw)
In-Reply-To: <CAL3LdT7+5FFbP5Rf1MoY2GJ9cQ0LJnecQb66ZA2ofwD28vy1jw@mail.gmail.com>
On 19/08/14 18:04, Jeff Kirsher wrote:
> On Mon, Aug 18, 2014 at 3:21 PM, Krzysztof Majzerowicz-Jaszcz
> <cristos@vipserv.org> wrote:
>> Fixed many errors/warnings and checks in e1000_ethtool.c reported by checkpatch.pl
>> Suggestions from Joe Perches and Alexander Duyck applied as well
>>
>> Signed-off-by: Krzysztof Majzerowicz-Jaszcz <cristos@vipserv.org>
>> ---
>> drivers/net/ethernet/intel/e1000/e1000_ethtool.c | 155 ++++++++++++-----------
>> 1 file changed, 79 insertions(+), 76 deletions(-)
>>
>
> Thanks Krzysztof, I will add your patch to my queue and I can fix up
> the patch title for you. :-)
>
Thank you :). Sorry for that patch title - I guess that 'first pancake is always spoiled'.
Nonetheless, that makes my first successful contribution to the kernel <yay> ;)
next prev parent reply other threads:[~2014-08-19 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 20:21 [PATCH v2] drivers: net: ethernet: intel: e1000: e1000_ethertoo.c coding style fixes Krzysztof Majzerowicz-Jaszcz
2014-08-19 16:04 ` Jeff Kirsher
2014-08-19 17:33 ` Krzysztof Majzerowicz-Jaszcz [this message]
2014-08-19 18:01 ` Joe Perches
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=53F38A84.3070702@vipserv.org \
--to=cristos@vipserv.org \
--cc=alexander.h.duyck@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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).