From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jt@hpl.hp.com
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.20-pre1
Date: 06 Aug 2002 19:48:22 +0100 [thread overview]
Message-ID: <1028659702.18156.185.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020806171736.GC11313@bougret.hpl.hp.com>
On Tue, 2002-08-06 at 18:17, Jean Tourrilhes wrote:
> 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'd prefer to be able to read the errors too but yes.
> 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.
By the time you asked I'd sent them
> 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.
I sent them to the maintainer.
IRDA SUBSYSTEM
P: Dag Brattli
M: Dag Brattli <dag@brattli.net>
L: linux-irda@pasta.cs.uit.no
W: http://irda.sourceforge.net/
S: Maintained
If thats wrong, then thats why you never found out.
next prev parent reply other threads:[~2002-08-06 17:25 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
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 [this message]
-- 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=1028659702.18156.185.camel@irongate.swansea.linux.org.uk \
--to=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®