[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190524141011.GA23514@lst.de>
Date: Fri, 24 May 2019 16:10:11 +0200
From: "hch@....de" <hch@....de>
To: Thomas Hellstrom <thellstrom@...are.com>
Cc: "hch@....de" <hch@....de>, "cai@....pw" <cai@....pw>,
"daniel@...ll.ch" <daniel@...ll.ch>,
"robin.murphy@....com" <robin.murphy@....com>,
"m.szyprowski@...sung.com" <m.szyprowski@...sung.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Linux-graphics-maintainer <Linux-graphics-maintainer@...are.com>,
"airlied@...ux.ie" <airlied@...ux.ie>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/vmwgfx: fix a warning due to missing dma_parms
On Fri, May 24, 2019 at 11:57:04AM +0000, Thomas Hellstrom wrote:
> It's a PCI device. The struct device * used in dma_map_sg() is the same
> as the &pci_dev->dev handed to the probe() callback. But at probe time,
> the struct device::dma_parms is non-NULL, at least on my system so
> there shouldn't really be a need to kzalloc() it.
Then there is something really odd going on in the OPs setup..
Powered by blists - more mailing lists