From: Vinod Koul <vinod.koul@intel.com>
To: Frank Mori Hess <fmh6jj@gmail.com>
Cc: dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dmaengine: pl330: flush before wait, and add dev burst support.
Date: Mon, 16 Apr 2018 21:03:17 +0530 [thread overview]
Message-ID: <20180416153315.GP6014@localhost> (raw)
In-Reply-To: <CAJz5Opdx26WZ-M8q2UayWz3o6SmR6VJMqUetQsX8k7YotK5XGg@mail.gmail.com>
On Sun, Apr 15, 2018 at 02:12:30PM -0400, Frank Mori Hess wrote:
> On Tue, Apr 10, 2018 at 11:37 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> >>
> >> Hi, what is the state of this patch? I just noticed in patchwork it
> >> is now listed as "Not applicable"? The original broken-by-wordwrap
> >> patch is listed as "Accepted"?
> >>
> >> https://patchwork.kernel.org/project/linux-dmaengine/list/?submitter=178687&state=*
> >
> > That is not correct state, my script would update as not applicable when it
> > doesn't find patch in my queue..
> >
> >> I found it has a bug handling dregs btw, I'll include a fix for that
> >> in the next version or as a follow-on patch as appropriate.
> >
> > Looks like I have missed this one somehow, so please update the patch with
> > fix and I shall look into it.
> >
>
> Ok, I tested the v4 patch and it turns out it was a false alarm about
> the bug in handling dregs. It works fine. I've registered in the
> dmaengine patchwork, and changed the state of the v4 patch back to
> "new".
Can you please repost this one after rebasing to dmaengine -next
--
~Vinod
prev parent reply other threads:[~2018-04-16 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1957017.QzKNMJJqD6@bear>
[not found] ` <20180306120259.GT15443@localhost>
2018-03-06 16:03 ` [PATCH v3] dmaengine: pl330: flush before wait, and add dev burst support Frank Mori Hess
2018-03-11 15:01 ` Vinod Koul
2018-03-11 16:10 ` Frank Mori Hess
2018-03-13 18:34 ` [PATCH v4] " Frank Mori Hess
2018-04-10 0:41 ` Frank Mori Hess
2018-04-10 15:37 ` Vinod Koul
2018-04-15 18:12 ` Frank Mori Hess
2018-04-16 15:33 ` Vinod Koul [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=20180416153315.GP6014@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fmh6jj@gmail.com \
--cc=linux-kernel@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).