From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux 2.4.20-pre1
Date: Tue, 6 Aug 2002 10:17:36 -0700 [thread overview]
Message-ID: <20020806171736.GC11313@bougret.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208060933070.7302-100000@freak.distro.conectiva>
On Tue, Aug 06, 2002 at 09:33:45AM -0300, Marcelo Tosatti wrote:
>
>
> On Mon, 5 Aug 2002, Jean Tourrilhes wrote:
>
> > Hi,
> >
> > Sorry to disturb, but it seems that kernel.org didn't pick up
> > 2.4.20-pre1 (or I'm looking at the wrong places).
> >
> > I'm asking because I've just finished testing my IrDA update
> > for 2.4.20, and you've just included some useless IrDA change that
> > probably render my patch worthless
>
> What you mean I included some useless IrDA patch?
Yep, tons of these :
-----------------------------------------------
- IRDA_DEBUG(4, __FUNCTION__ "(), speed=%d (was %d)\n", speed,
- self->speed);
+ IRDA_DEBUG(4, "%s(), speed=%d (was %d)\n", __FUNCTION__,
+ speed, self->speed);
-----------------------------------------------
Between this and fixing a Oops or Deadlock, I'll take the
second any day.
I don't care on those patch in general, I'm not a control
freak, except that being so pervasive they are guaranteed to screw up
my own patches. That's why yesterday I *explicitely* asked you and
Alan if anything was pending, so that I could avoid wasting my time
and instead wait for the next release doing something else.
I guess it's too late, I already wasted my afternoon.
The second thing that bugs me is that because those patches
pass behind my back, they won't get applied to *both* 2.4.X and
2.5.X. Because of that, keeping 2.4.X and 2.5.X in synch is an
exercise in futility.
But maybe you are finding that there is already too many IrDA
maintainers.
I'll send you the Wireless patches, and I'll try to respin the
IrDA patches this afternoon (i.e. please screw me again !).
Regards,
Jean
next prev parent reply other threads:[~2002-08-06 17:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 0:21 Jean Tourrilhes
2002-08-06 12:33 ` Marcelo Tosatti
2002-08-06 17:17 ` Jean Tourrilhes [this message]
2002-08-06 16:31 ` Marcelo Tosatti
2002-08-06 17:24 ` Jean Tourrilhes
2002-08-06 17:13 ` David S. Miller
2002-08-06 18:48 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-08-15 17:28 Matt_Domsch
2002-08-11 21:12 Matt_Domsch
[not found] <200208062329.g76NTqP30962@devserv.devel.redhat.com.suse.lists.linux.kernel>
2002-08-07 10:01 ` Andi Kleen
2002-08-07 11:50 ` Alan Cox
2002-08-06 23:29 Alan Cox
2002-08-05 22:40 Marcelo Tosatti
2002-08-06 0:20 ` Ben Greear
2002-08-06 11:32 ` Marcelo Tosatti
2002-08-06 12:26 ` David S. Miller
2002-08-06 16:45 ` Ben Greear
2002-08-06 14:58 ` Jason Lunz
2002-08-06 15:03 ` CaT
2002-08-06 21:05 ` Adrian Bunk
2002-08-07 11:09 ` David S. Miller
2002-08-07 0:21 ` J.A. Magallon
2002-08-07 1:08 ` J.A. Magallon
2002-08-07 1:56 ` Bryan Whitehead
2002-08-07 3:35 ` Tim Hockin
2002-08-11 8:57 ` Erik Andersen
2002-08-11 9:16 ` Christoph Hellwig
2002-08-11 9:40 ` Erik Andersen
2002-08-11 9:46 ` Erik Andersen
2002-08-11 19:46 ` Alan Cox
2002-08-11 18:49 ` Erik Andersen
2002-08-12 19:29 ` Paul P Komkoff Jr
2002-08-11 10:56 ` Erik Andersen
2002-08-17 19:51 ` Adrian Bunk
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=20020806171736.GC11313@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jt@hpl.hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®