From: Naveen Kaje <nkaje@codeaurora.org>
To: sricharan@codeaurora.org, dmaengine@vger.kernel.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm@vger.kernel.org
Cc: Naveen Kaje <nkaje@codeaurora.org>
Subject: Re: [PATCH 0/2] drivers: i2c: qup: Some misc fixes
Date: Wed, 4 May 2016 12:53:59 -0600 [thread overview]
Message-ID: <1462388039-8518-1-git-send-email-nkaje@codeaurora.org> (raw)
In-Reply-To: <1462166637-16778-1-git-send-email-sricharan@codeaurora.org>
From: Naveen Kaje <nkaje@codeaurora.org>
Hi Sricharan,
I tested these changes. They did not cause any regressions on QDF2432. Note that QDF2432 does not use DMA mode.
I based my patches (http://marc.info/?l=linux-i2c&m=146231797008963&w=2 and http://marc.info/?l=linux-i2c&m=146231798708969&w=2) on top of these fixes.
There are no merge conflicts.
Thanks,
Naveen
---
One for fixing the bug with CONFIG_DEBUG_SG enabled and another
to suspend the transfer for all errors instead of just for nack.
Sricharan R (2):
drivers: i2c: qup: Fix broken dma when CONFIG_DEBUG_SG is enabled.
drivers: i2c: qup: Fix error handling
drivers/i2c/busses/i2c-qup.c | 87 +++++++++++++++++++++-----------------------
1 file changed, 42 insertions(+), 45 deletions(-)
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2016-05-04 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 5:23 [PATCH 0/2] drivers: i2c: qup: Some misc fixes Sricharan R
2016-05-02 5:23 ` [PATCH 1/2] drivers: i2c: qup: Fix broken dma when CONFIG_DEBUG_SG is enabled Sricharan R
2016-05-05 17:33 ` Andy Gross
2016-05-02 5:23 ` [PATCH 2/2] drivers: i2c: qup: Fix error handling Sricharan R
2016-05-05 17:22 ` Andy Gross
2016-05-06 4:09 ` Sricharan
2016-05-04 18:53 ` Naveen Kaje [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=1462388039-8518-1-git-send-email-nkaje@codeaurora.org \
--to=nkaje@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sricharan@codeaurora.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).