From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net 0/3][pull request] Intel Wired LAN Driver Updates
Date: Wed, 27 Mar 2013 14:10:05 -0400 (EDT) [thread overview]
Message-ID: <20130327.141005.2019226838588462523.davem@davemloft.net> (raw)
In-Reply-To: <1364382333-14721-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 27 Mar 2013 04:05:30 -0700
> This series contains updates to e1000, ixgb and e1000e for Christoph.
>
> Christoph provides 3 patches to resolve missing dma_error_call's to
> provided Intel drivers which did not have this fix.
Pulled, thanks Jeff.
next prev parent reply other threads:[~2013-03-27 18:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 11:05 [net 0/3][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-03-27 11:05 ` [net 1/3] e1000: ethtool: Add missing dma_mapping_error-call in e1000_setup_desc_rings Jeff Kirsher
2013-03-27 11:05 ` [net 2/3] ixgb: Add missing dma_mapping_error-call in ixgb_alloc_rx_buffers Jeff Kirsher
2013-03-27 11:05 ` [net 3/3] e1000e: Add missing dma_mapping_error-call in e1000_alloc_jumbo_rx_buffers Jeff Kirsher
2013-03-27 18:10 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-19 15:40 [net 0/3][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-03-07 11:15 Jeff Kirsher
2013-03-07 20:19 ` David Miller
2012-10-09 10:13 Jeff Kirsher
2012-10-09 16:51 ` David Miller
2012-08-09 9:39 Peter P Waskiewicz Jr
2012-08-09 10:42 ` David Miller
2012-08-07 8:04 Peter P Waskiewicz Jr
2012-08-08 22:42 ` David Miller
2012-08-04 10:25 Peter P Waskiewicz Jr
2012-08-04 10:37 ` David Miller
2012-06-20 8:44 Jeff Kirsher
2012-06-20 22:09 ` David Miller
2012-06-06 4:08 Jeff Kirsher
2012-06-06 16:00 ` David Miller
2012-04-30 23:16 Jeff Kirsher
2012-04-03 22:28 Jeff Kirsher
2012-04-03 22:48 ` 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=20130327.141005.2019226838588462523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).