From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] nfp: few code improvements
Date: Thu, 30 Jun 2016 09:30:39 -0400 (EDT) [thread overview]
Message-ID: <20160630.093039.1888873867696709102.davem@davemloft.net> (raw)
In-Reply-To: <1467233755-14334-1-git-send-email-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Wed, 29 Jun 2016 21:55:52 +0100
> Three small patches for net-next. First and second patches
> improve the code quality by spelling things correctly and
> removing unused parameters. Third patch hooks-in standard
> kernel implementation of .get_link() in ethtool ops.
Series applied, thanks.
prev parent reply other threads:[~2016-06-30 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 20:55 [PATCH net-next 0/3] nfp: few code improvements Jakub Kicinski
2016-06-29 20:55 ` [PATCH net-next 1/3] nfp: correct name of control BAR define Jakub Kicinski
2016-06-29 20:55 ` [PATCH net-next 2/3] nfp: remove unused parameter from nfp_net_write_mac_addr() Jakub Kicinski
2016-06-29 20:55 ` [PATCH net-next 3/3] nfp: implement ethtool .get_link() callback Jakub Kicinski
2016-06-30 13:30 ` 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=20160630.093039.1888873867696709102.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.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).