From: Sebastian von Ohr <vonohr@smaract.com>
To: Radhey Shyam Pandey <radheys@xilinx.com>,
Vinod Koul <vkoul@kernel.org>,
Appana Durga Kedareswara Rao <appanad@xilinx.com>,
Michal Simek <michals@xilinx.com>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: RE: [PATCH] dmaengine: xilinx_dma: Add missing check for empty list
Date: Tue, 7 Apr 2020 07:52:08 +0000 [thread overview]
Message-ID: <c12c2321f9d5407698b9992b9a375966@smaract.com> (raw)
In-Reply-To: <CH2PR02MB7000C592992EEFBFB01D5735C7E30@CH2PR02MB7000.namprd02.prod.outlook.com>
> -----Original Message-----
> From: Radhey Shyam Pandey [mailto:radheys@xilinx.com]
> Sent: Friday, March 6, 2020 2:57 PM
> To: Vinod Koul <vkoul@kernel.org>; Sebastian von Ohr
> <vonohr@smaract.com>; Appana Durga Kedareswara Rao
> <appanad@xilinx.com>; Michal Simek <michals@xilinx.com>
> Cc: dmaengine@vger.kernel.org
> Subject: RE: [PATCH] dmaengine: xilinx_dma: Add missing check for empty
> list
>
> Sure, we will test it. Changes look fine. Though had a question in mind,
> for a generic fix to this problem, should we make locking mandatory for
> all cookie helper functions? Or is there any limitation?
Any progress on the testing? If you need help reproducing the issue please let me know.
next prev parent reply other threads:[~2020-04-07 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 13:05 [PATCH] dmaengine: xilinx_dma: Add missing check for empty list Sebastian von Ohr
2020-03-06 13:34 ` Vinod Koul
2020-03-06 13:57 ` Radhey Shyam Pandey
2020-03-11 9:16 ` Vinod Koul
2020-04-07 7:52 ` Sebastian von Ohr [this message]
2020-04-07 16:03 ` Radhey Shyam Pandey
2020-04-08 7:12 ` Sebastian von Ohr
2020-04-08 14:06 ` Radhey Shyam Pandey
2020-04-08 15:19 ` Sebastian von Ohr
2020-04-09 7:40 ` Radhey Shyam Pandey
2020-04-15 16:12 ` Vinod Koul
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=c12c2321f9d5407698b9992b9a375966@smaract.com \
--to=vonohr@smaract.com \
--cc=appanad@xilinx.com \
--cc=dmaengine@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=radheys@xilinx.com \
--cc=vkoul@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).