linux-kernel.vger.kernel.org archive mirror
 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:55:27 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10307141342420.28472-100000@gate.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307141533330.8994@freak.distro.conectiva>



On Mon, 14 Jul 2003, Marcelo Tosatti wrote:

> 
> Ah really? I though that his changes were not merged in your 0.1.8 patch.
> 
> So can I just revert his patch and accept your instead that all of his
> stuff is in ? Whoaa, great.

Here is an xcept from ChangeLong section of the driver from the patch I
sent you:

+ *     2003-04-12      Mac PowerBook sleep fixes, Benjamin Herrenschmidt,
+ *                     0.1.8

I agree this isn't very descriptive of this other fixes and I can change
that, but a lot of his Mac changes have been merged in, but apparently
nobody has taken the time to actually look at that patch.  If there are
things that are missing then I asked him to tell me, which he has not so I
assume there are none.

> Ani, I received complains that you were not accepting patches from Ben. He
> needs that code in.

This is not true, see the above.  Also, its hard to "accept patches" from
people if you do NOT recieve any patches from them!  Ben's style is to get
the maintainers of drivers to go around and search for his personal tree
and do their own diffs from that tree, instead of him sending a patch to
the maintainer.

> > 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.
> 
> I prefer playing no silly games in the 2.4 stable series, as I've been
> trying to do so far. If you had accepted Ben's changes in the first place
> I wouldnt need to apply his patch.

I did accept most all of his changes when this patch was made (originally
I sent it May 12, which you did not merge into 2.4.21, probably because I
sent it during the RC stange, but after that you lost the patch ?).  Since
that time, I assume Ben has made some other changes, which I have not
recieved any word about.

Please don't accuse people of not accpeting patches when that is simply 
not true, as it can be easily said for you too.



  reply	other threads:[~2003-07-14 18:45 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 ` Marcelo Tosatti
2003-07-14 18:30   ` ajoshi
2003-07-14 18:40     ` Marcelo Tosatti
2003-07-14 18:55       ` ajoshi [this message]
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.10307141342420.28472-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 \
    --subject='Re: radeonfb patch for 2.4.22...' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).