All of lore.kernel.org
 help / color / mirror / Atom feed
From: <ajoshi@kernel.crashing.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>, benh@kernel.crashing.org
Subject: Re: radeonfb patch for 2.4.22...
Date: Mon, 14 Jul 2003 13:30:16 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10307141315170.28093-100000@gate.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307141506020.8994@freak.distro.conectiva>



On Mon, 14 Jul 2003, Marcelo Tosatti wrote:
> 
> On Mon, 14 Jul 2003 ajoshi@kernel.crashing.org wrote:
> 
> >
> > Hi Marcelo,
> >
> > Is there any particular reason why you decided to merge Ben H.'s radeonfb
> > update instead of the one I sent you?
> 
> I've decided to CC lkml because I think there are other people interested
> in this discussion.
> 
> I merged his version because he sent me your update (0.1.8) plus his code
> (which are useful fixes he has been working on).

Which is what the original 0.1.8 patch included, his fixes were included.

> 
> It seems things are broken now due to a missing header, but he also sent
> me that.

There was no missing header, if you see the patch I sent you (about 3
times), the header file is in there.

> 
> Do you have any objections to his fixes ?
> 

Besides the obvious version changes and difficulty maintaining a driver
where anyone seems to be able to change it in the official tree, the
objections were deteremined and fixed in the patch I sent you.

Refresh my memory as it seems things have  changed in kernel patch
submission process:

There is someone called a driver author or maintainer, this person
recieves patches for fixes from various people, he/she then compiles them
into a single patch and submits it to the kernel tree maintiner.  However
nowdays it seems the kernel tree maintainer has the descretion to accept
patches from anyone how puts up a fight, is this the case nowdays?  

If so then please let me know, so I don't waste anymore of my time on this
driver and let someone else play these silly games and maintain it.


ani


  reply	other threads:[~2003-07-14 18:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10307141237001.27519-100000@gate.crashing.org>
2003-07-14 18:11 ` radeonfb patch for 2.4.22 Marcelo Tosatti
2003-07-14 18:30   ` ajoshi [this message]
2003-07-14 18:40     ` Marcelo Tosatti
2003-07-14 18:55       ` ajoshi
2003-07-14 19:11         ` Marcelo Tosatti
2003-07-14 19:34           ` Damian Kolkowski
2003-07-14 19:36             ` Marcelo Tosatti
2003-07-15  8:47         ` Benjamin Herrenschmidt
2003-07-15  7:44       ` Benjamin Herrenschmidt
2003-07-15 12:02         ` Peter Osterlund
2003-07-15 13:43           ` Benjamin Herrenschmidt
2003-07-16 10:59 Eric Blade
2003-07-17 17:29 ` James Simmons
2003-07-17 22:43   ` Eric Blade
2003-07-18 17:42     ` James Simmons

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.10.10307141315170.28093-100000@gate.crashing.org \
    --to=ajoshi@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.