From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
linux-net-drivers <linux-net-drivers@solarflare.com>,
Joe Perches <joe@perches.com>
Subject: pull request: sfc-next 2012-01-30
Date: Mon, 30 Jan 2012 18:20:27 +0000 [thread overview]
Message-ID: <1327947627.2595.7.camel@bwh-desktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
The following changes since commit 30088a25e9c4dc1f8bd5c48b14a18633441b5481:
Merge branch 'for-davem' of git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next (2012-01-29 16:11:26 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next.git for-davem
(commit 06e63c57acbb1df7c35ebe846ae416a8b88dfafa)
These address the review comments on Friday's changes.
Ben.
Ben Hutchings (2):
sfc: MTD: Leave the DEBUG macro alone
sfc: Use a more sensible cast in efx_rx_buf_offset()
drivers/net/ethernet/sfc/mtd.c | 1 -
drivers/net/ethernet/sfc/rx.c | 2 +-
2 files changed, 1 insertions(+), 2 deletions(-)
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2012-01-30 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 18:20 Ben Hutchings [this message]
2012-01-30 18:21 ` [PATCH net-next 1/2] sfc: MTD: Leave the DEBUG macro alone Ben Hutchings
2012-01-30 18:22 ` [PATCH net-next 2/2] sfc: Use a more sensible cast in efx_rx_buf_offset() Ben Hutchings
2012-01-30 20:47 ` pull request: sfc-next 2012-01-30 David Miller
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=1327947627.2595.7.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=joe@perches.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).