mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@linux.ie>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [rfc][patch] DRM initial function table support.
Date: Wed, 1 Sep 2004 00:39:24 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0409010033370.31241@skynet> (raw)
In-Reply-To: <20040831152015.GC22978@redhat.com>

>
> I like this. Lots.
> Mostly because of this..
>
> (16:14:11:davej@delerium:~)$ grep ^-# foo.diff  | wc -l
> 87

You think that one is good
 grep ^-# current_diffs | wc -l
496

is for my current CVS tree vs the in-kernel DRM ;-),

> 	.preinit = gamma_driver_preinit,
> 	.pretakedown = gamma_driver_pretakedown,
> 	.dma_ready = gamma_driver_dma_ready,
> 	.dma_quiescent = gamma_driver_dma_quiescent,
> 	.dma_flush_block_and_flush = gamma_flush_block_and_flush,
> 	.dma_flush_unblock = gamma_flush_unblock,
> };

With this patch it would be okay, with some of the functions I added to
the table later, I had to set some defaults before calling the driver
function, and also added another setting for AGP/MTRR type stuff to the
device independent structure that needed to be set, I'll try and get the
rest of the patches for macro removal merged up and then perhaps you could
take a look at it (or take a look at CVS now) and we can cleanup the style
if we still think it is necessary.. btw the setting ptrs in a fn table is
the DRI/Mesa way of doing things .. so we have a bit of where two worlds
collide... :-)

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person


      parent reply	other threads:[~2004-08-31 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 13:11 Dave Airlie
2004-08-31 15:20 ` Dave Jones
2004-08-31 16:07   ` Ian Romanick
2004-08-31 17:01     ` Christoph Hellwig
2004-08-31 17:52       ` Ian Romanick
2004-08-31 23:39   ` Dave Airlie [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=Pine.LNX.4.58.0409010033370.31241@skynet \
    --to=airlied@linux.ie \
    --cc=davej@redhat.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

all inboxes | Powered by JetHome®