From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Jiang <dave.jiang@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: manual merge of the dmaengine tree with the dmaengine-fixes tree
Date: Wed, 5 Jan 2022 12:49:54 +0530 [thread overview]
Message-ID: <YdVGmkzgUmvPDmlE@matsya> (raw)
In-Reply-To: <20220105100407.69b16fe2@canb.auug.org.au>
On 05-01-22, 10:04, Stephen Rothwell wrote:
> Hi Dave,
>
> On Tue, 4 Jan 2022 14:41:00 -0700 Dave Jiang <dave.jiang@intel.com> wrote:
> >
> > >> + */
> > >> + list_for_each_entry_safe(d, t, &flist, list) {
> > >> + list_del_init(&d->list);
> > >> - complete_desc(d, IDXD_COMPLETE_NORMAL);
> > >> ++ idxd_dma_complete_txd(d, IDXD_COMPLETE_NORMAL, false);
> > > Is "false" correct here?
> >
> > Hi Geert, took a closer look today. I believe it should be 'true'
> > here since this is a normal completion that needs to release the
> > descriptors. Sorry about the previous incorrect response.
>
> I have updated my resolution from today. Thanks for the feedback.
I have merged fixes into next as well, so this should not be required
tomorrow.
Dave pls test..
--
~Vinod
next prev parent reply other threads:[~2022-01-05 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 17:24 linux-next: manual merge of the dmaengine tree with the dmaengine-fixes tree broonie
2021-12-28 9:09 ` Geert Uytterhoeven
2021-12-28 14:54 ` Jiang, Dave
2022-01-04 21:41 ` Dave Jiang
2022-01-04 23:04 ` Stephen Rothwell
2022-01-05 7:19 ` Vinod Koul [this message]
2022-01-06 23:18 ` Dave Jiang
-- strict thread matches above, loose matches on Subject: below --
2022-04-12 2:42 Stephen Rothwell
2022-04-12 11:16 ` Vinod Koul
2021-07-15 1:40 Stephen Rothwell
2020-11-19 3:29 Stephen Rothwell
2020-12-14 19:58 ` Stephen Rothwell
2020-12-15 4:33 ` Vinod Koul
2020-07-06 3:56 Stephen Rothwell
2020-07-06 4:23 ` Dave Jiang
2020-07-06 4:41 ` Vinod Koul
2020-07-06 6:03 ` Stephen Rothwell
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=YdVGmkzgUmvPDmlE@matsya \
--to=vkoul@kernel.org \
--cc=broonie@kernel.org \
--cc=dave.jiang@intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).