From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: Pull request: sfc-next 2013-12-12
Date: Sat, 14 Dec 2013 01:11:40 -0500 (EST) [thread overview]
Message-ID: <20131214.011140.1782125225508708522.davem@davemloft.net> (raw)
In-Reply-To: <1386888977.1516.337.camel@bwh-desktop.uk.level5networks.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Thu, 12 Dec 2013 22:56:17 +0000
> An assortment of changes for Linux 3.14:
>
> 1. Merge the sfc fixes that you have already merged into net.git.
> (The branch point for those was such that this does not bring in any
> other changes.)
> 2. Reduce log level for a generally useless warning message, from
> Robert Stonehouse.
> 3. Include BISTs in ethtool offline self-test for EF10 and recover from
> BISTs initiated through other functions, from Jon Cooper.
> 4. Improve a sanity check on RX completions.
> 5. Avoid incrementing RX dropped count while the interface is down, from
> Jon Cooper.
> 6. Improve hardware sensor naming and log messages, from Edward Cree.
> 7. Log all unexpected errors returned by firmware, from Edward Cree.
> 8. Expose another NVRAM partition to userland.
> 9. Some refactoring of the PTP code in preparation for EF10 support.
> 10. Various minor cleanups.
Pulled, thanks Ben.
prev parent reply other threads:[~2013-12-14 6:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 22:56 Pull request: sfc-next 2013-12-12 Ben Hutchings
2013-12-12 22:59 ` [PATCH net-next 01/16] sfc: Demote "MC Scheduler error" messages Ben Hutchings
2013-12-12 22:59 ` [PATCH net-next 02/16] sfc: Update MCDI protocol definitions Ben Hutchings
2013-12-12 22:59 ` [PATCH net-next 03/16] sfc: Add MC BISTs to ethtool offline self test on EF10 Ben Hutchings
2013-12-12 23:00 ` [PATCH net-next 04/16] sfc: Tighten the check for RX merged completion events Ben Hutchings
2013-12-12 23:00 ` [PATCH net-next 05/16] sfc: Make initial fill of RX descriptors synchronous Ben Hutchings
2013-12-12 23:00 ` [PATCH net-next 06/16] sfc: Correct RX dropped count for drops while interface is down Ben Hutchings
2013-12-12 23:01 ` [PATCH net-next 07/16] sfc: Report units in sensor warnings Ben Hutchings
2013-12-12 23:01 ` [PATCH net-next 08/16] sfc: Revise sensor names to be more understandable and consistent Ben Hutchings
2013-12-12 23:01 ` [PATCH net-next 09/16] sfc: Add new sensor names Ben Hutchings
2013-12-12 23:02 ` [PATCH net-next 10/16] sfc: Log all unexpected MCDI errors Ben Hutchings
2013-12-12 23:02 ` [PATCH net-next 11/16] sfc: Map MCDI error MC_CMD_ERR_ENOTSUP to Linux EOPNOTSUPP Ben Hutchings
2013-12-12 23:02 ` [PATCH net-next 12/16] sfc: Fold efx_flush_all() into efx_stop_port() and update comments Ben Hutchings
2013-12-12 23:02 ` [PATCH net-next 13/16] sfc: Expose NVRAM_PARTITION_TYPE_LICENSE on EF10 Ben Hutchings
2013-12-12 23:03 ` [PATCH net-next 14/16] sfc: Return EBUSY for filter insertion on EF10, matching Falcon/Siena Ben Hutchings
2013-12-12 23:03 ` [PATCH net-next 15/16] sfc: Split PTP multicast filter insertion/removal out of efx_ptp_{start,stop}() Ben Hutchings
2013-12-12 23:03 ` [PATCH net-next 16/16] sfc: Remove dependency of PTP on having a dedicated channel Ben Hutchings
2013-12-14 6:11 ` 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=20131214.011140.1782125225508708522.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.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).