On Sun, Dec 15, 2013 at 09:24:11AM +, Chris Wilson wrote:
> On Sat, Dec 14, 2013 at 05:42:42PM -0800, Ben Widawsky wrote:
> > On Sat, Dec 14, 2013 at 09:45:34PM +, Chris Wilson wrote:
> > > On Fri, Dec 13, 2013 at 08:15:57PM -0800, Ben Widawsky wrote:
> > > > Having the ring id all set up w
On Sat, Dec 14, 2013 at 05:42:42PM -0800, Ben Widawsky wrote:
> On Sat, Dec 14, 2013 at 09:45:34PM +, Chris Wilson wrote:
> > On Fri, Dec 13, 2013 at 08:15:57PM -0800, Ben Widawsky wrote:
> > > Having the ring id all set up will allow us to use some macro shortcuts
> > > during ringbuffer init.
On Sat, Dec 14, 2013 at 09:45:34PM +, Chris Wilson wrote:
> On Fri, Dec 13, 2013 at 08:15:57PM -0800, Ben Widawsky wrote:
> > Having the ring id all set up will allow us to use some macro shortcuts
> > during ringbuffer init. Admittedly it leaves the code a bit confusing,
> > having the initial
On Fri, Dec 13, 2013 at 08:15:57PM -0800, Ben Widawsky wrote:
> Having the ring id all set up will allow us to use some macro shortcuts
> during ringbuffer init. Admittedly it leaves the code a bit confusing,
> having the initialization of the id member in a separate place - but I
> think the savin
Having the ring id all set up will allow us to use some macro shortcuts
during ringbuffer init. Admittedly it leaves the code a bit confusing,
having the initialization of the id member in a separate place - but I
think the savings is worth it.
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i91
