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-2.6 2011-05-12
Date: Thu, 12 May 2011 16:30:30 -0400 (EDT) [thread overview]
Message-ID: <20110512.163030.1127683523653779733.davem@davemloft.net> (raw)
In-Reply-To: <1305216428.5214.13.camel@bwh-desktop>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Thu, 12 May 2011 17:07:08 +0100
> The following changes since commit ff538818f4a82c4cf02d2d6bd6ac5c7360b9d41d:
>
> sysctl: net: call unregister_net_sysctl_table where needed (2011-05-02 16:12:14 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-2.6.git sfc-2.6.39
>
> Ben Hutchings (1):
> sfc: Always map MCDI shared memory as uncacheable
>
> Sorry for sending this so late. I was really hoping to get to the
> bottom of this issue and find a simple fix.
Pulled, thanks Ben.
prev parent reply other threads:[~2011-05-12 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 16:07 pull request: sfc-2.6 2011-05-12 Ben Hutchings
2011-05-12 16:09 ` [PATCH net-2.6] sfc: Always map MCDI shared memory as uncacheable Ben Hutchings
2011-05-12 20: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=20110512.163030.1127683523653779733.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).