public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Whitwell <keith@tungstengraphics.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	dri-devel <dri-devel@lists.sourceforge.net>,
	Xserver development <xorg@freedesktop.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: New DRM driver model - gets rid of DRM() macros!
Date: Wed, 29 Sep 2004 14:35:48 +0100	[thread overview]
Message-ID: <415ABA34.9080608@tungstengraphics.com> (raw)
In-Reply-To: <20040929143129.A12651@infradead.org>

Christoph Hellwig wrote:
> On Wed, Sep 29, 2004 at 02:29:24PM +0100, Keith Whitwell wrote:
> 
>>Christoph Hellwig wrote:
>>
>>
>>> - drm_flush is a noop.  a NULL ->flush does the same thing, just easier
>>> - dito or ->poll
>>> - dito for ->read
>>
>>Pretty sure you couldn't get away with null for these in 2.4, at least.
> 
> 
> Umm, of course you could.  There's only a hanfull instance defining a
> ->flush at all.  Similarly all file_ops for regular files and many char
> devices don't have ->poll.  no ->read is pretty rare but 2.4 chæcks it
> aswell.

I tried it, led to crashes (panics, I guess) & the change had to be reverted. 
  On reverting the crashes stopped.  This was for poll and read:

revision 1.12
date: 2003-04-23 23:42:28 +0000;  author: keithw;  state: Exp;  lines: +13 -0
Install dummy/noop read & poll fops unless the driver has replacements.
----------------------------
revision 1.11
date: 2003-04-22 08:06:13 +0000;  author: keithw;  state: Exp;  lines: +0 -94
remove DRM read, poll and write_string


I didn't do any more investigation & the behaviour may well be different 
nowadays.

Keith

  reply	other threads:[~2004-09-29 13:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 15:54 New DRM driver model - gets rid of DRM() macros! Jon Smirl
2004-09-28 16:56 ` Ian Romanick
2004-09-28 17:28   ` Jon Smirl
2004-09-28 19:35   ` Helge Hafting
2004-09-28 23:10 ` Dave Airlie
2004-09-29  1:27   ` Jon Smirl
2004-09-29  2:11     ` Dave Airlie
2004-09-29  5:25       ` Jon Smirl
2004-09-29 12:37 ` Christoph Hellwig
2004-09-29 11:59   ` Alan Cox
2004-09-29 13:16     ` Dave Airlie
2004-09-29 13:29   ` Keith Whitwell
2004-09-29 13:31     ` Christoph Hellwig
2004-09-29 13:35       ` Keith Whitwell [this message]
2004-09-29 14:12         ` Keith Whitwell
2004-09-29 14:16           ` Christoph Hellwig
2004-09-29 14:27             ` Keith Whitwell
2004-09-29 14:39               ` Keith Whitwell
2004-09-29 19:16                 ` Keith Packard
2004-09-30 18:10         ` Jon Smirl
2004-09-29 13:41   ` Dave Airlie
2004-10-01  5:15   ` Jon Smirl
2004-09-29 14:25 ` Keith Whitwell
2004-09-30  0:00   ` Eric Anholt
2004-09-29 21:52 ` Felix Kühling
2004-09-29 21:02   ` Alan Cox
2004-09-29 23:25   ` Jon Smirl
     [not found]     ` <20041006133714.GA26860@localdomain>
     [not found]       ` <9e47339104100609307307f8ea@mail.gmail.com>
     [not found]         ` <20041006211922.GA5167@localdomain>
2004-10-06 21:46           ` Code status (Was: New DRM driver model - gets rid of DRM() macros!) Ian Romanick

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=415ABA34.9080608@tungstengraphics.com \
    --to=keith@tungstengraphics.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=hch@infradead.org \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg@freedesktop.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