From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Arvind Kumar <arvindkumar@vmware.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
VMware PV-Drivers <pv-drivers@vmware.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] VMW_PVSCSI: Fix the issue of DMA-API related warnings.
Date: Thu, 11 Jun 2015 06:23:54 -0700 [thread overview]
Message-ID: <1434029034.2228.3.camel@HansenPartnership.com> (raw)
In-Reply-To: <CA+5PVA5tghb=ZhUHwt7A6+yK1hmcFzPbwYL1BN2wkd76p=o54Q@mail.gmail.com>
On Thu, 2015-06-11 at 08:32 -0400, Josh Boyer wrote:
> On Fri, Mar 21, 2014 at 2:08 PM, Arvind Kumar <arvindkumar@vmware.com> wrote:
> > The driver is missing calls to pci_dma_mapping_error() after
> > performing the DMA mapping, which caused DMA-API warning to
> > show up in dmesg's output. Though that happens only when
> > DMA_API_DEBUG option is enabled. This change fixes the issue
> > and makes pvscsi_map_buffers() function more robust.
> >
> > Signed-off-by: Arvind Kumar <arvindkumar@vmware.com>
> > Cc: Josh Boyer <jwboyer@fedoraproject.org>
>
> This patch has been sent and pinged for 3 months now. It's gotten no
> comments at all. Should we send it to Linus so it actually gets
> picked up?
It's waiting for someone to review it. If you're interested in it, have
you reviewed it? In which case just add your reviewed by and we're
ready to go.
James
next prev parent reply other threads:[~2015-06-11 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 18:08 [PATCH] VMW_PVSCSI: Fix the issue of DMA-API related warnings Arvind Kumar
2014-04-14 18:17 ` [Pv-drivers] " Arvind Kumar
2014-05-15 17:59 ` Arvind Kumar
2015-06-11 12:32 ` Josh Boyer
2015-06-11 13:23 ` James Bottomley [this message]
2015-06-11 18:11 ` [Pv-drivers] " Thomas Hellstrom
2015-07-07 21:00 ` Arvind Kumar
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=1434029034.2228.3.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=arvindkumar@vmware.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=torvalds@linux-foundation.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).