From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com, guru.anbalagane@oracle.com
Subject: Re: [net-next 0/2][pull request] 100GbE Intel Wired LAN Driver Updates 2016-10-02
Date: Mon, 03 Oct 2016 23:29:02 -0400 (EDT) [thread overview]
Message-ID: <20161003.232902.336303351855675086.davem@davemloft.net> (raw)
In-Reply-To: <1475476843-23405-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Sun, 2 Oct 2016 23:40:41 -0700
> This series contains updates to fm10k only.
>
> Jake fixes an issue where PTP applications requesting software timestamps
> may complain that the requested mode is not supported, so add a generic
> callback for those drivers that have software transmit timestamp support
> enabled. Then provides a trivial cleanup where a code was not wrapped
> properly. Got make sure that code looks good in a 80 character limit.
>
> The following are changes since commit 7c70c4f8b2bf5ed777120f3d70efe35e64930c10:
> cxgb4: unexport cxgb4_dcb_enabled
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE
Pulled.
prev parent reply other threads:[~2016-10-04 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 6:40 [net-next 0/2][pull request] 100GbE Intel Wired LAN Driver Updates 2016-10-02 Jeff Kirsher
2016-10-03 6:40 ` [net-next 1/2] fm10k: use generic ethtool_op_get_ts_info callback Jeff Kirsher
2016-10-03 6:40 ` [net-next 2/2] fm10k: wrap long line for alloc_workqueue Jeff Kirsher
2016-10-04 3:29 ` 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=20161003.232902.336303351855675086.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=guru.anbalagane@oracle.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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