From: Dave Airlie <airlied@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mark inter_module_* deprecated
Date: Thu, 23 Sep 2004 11:53:23 +1000 [thread overview]
Message-ID: <21d7e99704092218531ec19260@mail.gmail.com> (raw)
In-Reply-To: <20040919101337.GA5910@lst.de>
On Sun, 19 Sep 2004 12:13:38 +0200, Christoph Hellwig <hch@lst.de> wrote:
> These had been officially deprecated since Rusty's module rewrite, but
> never got the __deprecated marker. The only remaining users are drm and
> mtd, so we'll get some warnings for common builds. But maybe that's the
> only way to get the drm people to fix the mess :)
>
It'll piss a few people off but it won't create time, the only thing
stopping the drm from getting this stuff out of the way is time, there
are two uses in the DRM, one is the agp one, this is easy, Rusty
posted a patch for this and I'll probably merge it up after the next
kernel release.. the other use requries moving to some sort of DRM
in-kernel core, again I'd rather do this at the start of a kernel
release cycle as it'll require a bit of testing to make sure we don't
break anything....
Most of this stuff is easier if we weren't waiting on Alans vga class
support driver to turn up as without it the DRM CVS is blocked, and no
DRM developer really wants to start hacking on the vga class stuff as
we don't believe it is where our time is best spent until Alan gets
code merged into the kernel and gets the fb guys to convert all their
drivers... I've already got a patch for converting the DRM to a fixed
up version of his last patch...
Dave.
next prev parent reply other threads:[~2004-09-23 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 10:13 [PATCH] mark inter_module_* deprecated Christoph Hellwig
2004-09-23 1:53 ` Dave Airlie [this message]
2004-09-23 16:13 ` Alan Cox
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=21d7e99704092218531ec19260@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--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