[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF6AEGvN6SCfrmfui3-wT3maPGhDYFwEzEOYp=L_ySXa7bLWgQ@mail.gmail.com>
Date: Thu, 29 Nov 2018 13:44:11 -0500
From: Rob Clark <robdclark@...il.com>
To: hch@....de
Cc: Vivek Gautam <vivek.gautam@...eaurora.org>,
David Airlie <airlied@...ux.ie>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
freedreno <freedreno@...ts.freedesktop.org>,
Tomasz Figa <tfiga@...omium.org>,
Archit Taneja <architt@...eaurora.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Robin Murphy <robin.murphy@....com>,
Jordan Crouse <jcrouse@...eaurora.org>,
Sean Paul <seanpaul@...omium.org>
Subject: Re: [PATCH v3 1/1] drm: msm: Replace dma_map_sg with dma_sync_sg*
On Thu, Nov 29, 2018 at 10:53 AM Christoph Hellwig <hch@....de> wrote:
>
> On Thu, Nov 29, 2018 at 09:25:43AM -0500, Rob Clark wrote:
> > > As I told you before: hell no. If you spent the slightest amount of
> > > actually trying to understand what you are doing here you'd know this
> > > can't work. Just turn on dma debugging and this will blow up in your
> > > face.
> >
> > you can tone it down.. we weren't the ones who created the dma/iommu
> > mess, we are just trying to find a way to work around it
>
> But you don't listen and take someone busy for a day as approval,
> which is absolutely not the case. Please wait for a day or two for
> people to respond instead of forcing already NACKed patches again in
> an act of passive agression.
I'm not sending my pull-req to Dave tomorrow (or even the day after
;-)), so there is ofc still time for people to respond.
BR,
-R
Powered by blists - more mailing lists