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-2.6 2010-12-21
Date: Tue, 21 Dec 2010 12:17:53 -0800 (PST) [thread overview]
Message-ID: <20101221.121753.112583156.davem@davemloft.net> (raw)
In-Reply-To: <1292942817.3256.2.camel@bwh-desktop>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Tue, 21 Dec 2010 14:46:57 +0000
> The following changes since commit cf78f8ee3de7d8d5b47d371c95716d0e4facf1c4:
>
> Merge branch 'for-davem' of git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next-2.6 (2010-12-10 10:20:43 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next-2.6.git for-davem
>
> Some overdue cleanup of the TX path.
Pulled, thanks a lot Ben.
prev parent reply other threads:[~2010-12-21 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 14:46 pull request: sfc-next-2.6 2010-12-21 Ben Hutchings
2010-12-21 14:48 ` [PATCH net-next-2.6 1/2] sfc: Remove unused field and comment on a previously removed field Ben Hutchings
2010-12-21 14:49 ` [PATCH net-next-2.6 2/2] sfc: Remove ancient support for nesting of TX stop Ben Hutchings
2010-12-21 20:17 ` 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=20101221.121753.112583156.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).