Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <20180410153718.GS6014@localhost>
References: <20180311150151.GB15443@localhost> <2863317.1ZoR41yQkl@bear>
 <CAJz5OpdV1=L3fsQESZusAp8Cir9wE-VqPXqBa=zOGjBcPE78DA@mail.gmail.com> <20180410153718.GS6014@localhost>
From:   Frank Mori Hess <fmh6jj@gmail.com>
Date:   Sun, 15 Apr 2018 14:12:30 -0400
Message-ID: <CAJz5Opdx26WZ-M8q2UayWz3o6SmR6VJMqUetQsX8k7YotK5XGg@mail.gmail.com>
Subject: Re: [PATCH v4] dmaengine: pl330: flush before wait, and add dev burst support.
To:     Vinod Koul <vinod.koul@intel.com>
Cc:     dmaengine@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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".


-- 
Frank