From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Christoph Paasch <christoph.paasch@uclouvain.be>
Cc: Bruce Allan <bruce.w.allan@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/3] e1000: ethtool: Add missing dma_mapping_error-call in e1000_setup_desc_rings
Date: Tue, 19 Mar 2013 17:47:24 -0700 [thread overview]
Message-ID: <1363740444.2069.51.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1363429925-12724-2-git-send-email-christoph.paasch@uclouvain.be>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Sat, 2013-03-16 at 11:32 +0100, Christoph Paasch wrote:
>
> After dma_map_single, dma_mapping_error must be called.
>
> Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
> ---
> drivers/net/ethernet/intel/e1000/e1000_ethtool.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
Added to my e1000 patch queue
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-20 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 10:32 [PATCH 0/3] net/intel: Add missing calls to dma_mapping_error Christoph Paasch
2013-03-16 10:32 ` [PATCH 1/3] e1000: ethtool: Add missing dma_mapping_error-call in e1000_setup_desc_rings Christoph Paasch
2013-03-20 0:47 ` Jeff Kirsher [this message]
2013-03-16 10:32 ` [PATCH 2/3] ixgb: Add missing dma_mapping_error-call in ixgb_alloc_rx_buffers Christoph Paasch
2013-03-20 0:48 ` Jeff Kirsher
2013-03-16 10:32 ` [PATCH 3/3] e1000e: Add missing dma_mapping_error-call in e1000_alloc_jumbo_rx_buffers Christoph Paasch
2013-03-20 0:47 ` Jeff Kirsher
2013-03-20 0:46 ` [PATCH 0/3] net/intel: Add missing calls to dma_mapping_error Jeff Kirsher
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=1363740444.2069.51.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--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).