From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Ian Romanick <idr@us.ibm.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [Dri-devel] Re: DRM reorganization
Date: Tue, 16 Mar 2004 19:21:01 +0000 [thread overview]
Message-ID: <20040316192101.GA17979@redhat.com> (raw)
In-Reply-To: <20040315163131.1b03b49f.akpm@osdl.org>
On Mon, Mar 15, 2004 at 04:31:31PM -0800, Andrew Morton wrote:
> I've had a 130k DRM patch in -mm since February 8th. Presumably it's out
> of date. As far as I know nobody is pushing more recent patches upstream.
The patch you've been carrying for a while has a number of bogons,
like duplicating pci.ids inside the radeon driver for no good reason.
> What's the process here, and who should I be dealing with?
In the past most of the merges were done by Linus. I don't recall
seeing a 'dri maintainer' per se ever sending resync patches.
Dave
next prev parent reply other threads:[~2004-03-16 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:15 DRM reorganization Ian Romanick
2004-03-15 23:26 ` Andrew Morton
2004-03-15 23:51 ` [Dri-devel] " Alex Deucher
2004-03-16 0:15 ` Ian Romanick
2004-03-16 0:31 ` Andrew Morton
2004-03-16 19:21 ` Dave Jones [this message]
2004-03-16 0:42 ` Jon Smirl
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=20040316192101.GA17979@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.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