Linux bluetooth development
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Justin Karneges <justin-qt@affinix.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dtl1_cs suspend bug
Date: Tue, 23 Sep 2003 13:49:47 +0100	[thread overview]
Message-ID: <1064321387.3793.216.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <200309230508.07932.justin-qt@affinix.com>

On Tue, 2003-09-23 at 05:08 -0700, Justin Karneges wrote:
> I don't think I want to see another info->link or mod_timer again in my life.
> 
> I hereby commend anyone who manages to do kernel development.  Personally, I'd 
> like to start throwing things out the window.

Most of the kernel is a _lot_ saner than the PCMCIA code.

As for the PCMCIA code, I heartily recommend printing it all out on
paper, ritually burning it, urinating on the ashes, and participating in
the rewrite that's going into 2.6 :)

-- 
dwmw2




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2003-09-23 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 11:08 [Bluez-devel] dtl1_cs suspend bug Justin Karneges
2003-09-23 12:08 ` Justin Karneges
2003-09-23 12:19   ` Marcel Holtmann
2003-09-23 21:09     ` Justin Karneges
2003-09-23 21:37       ` Marcel Holtmann
2003-09-23 21:44         ` Justin Karneges
2003-09-23 22:17           ` Marcel Holtmann
2003-09-23 23:48             ` Justin Karneges
2003-09-24  1:35               ` Marcel Holtmann
2003-09-24  6:06                 ` Justin Karneges
2003-09-24  9:36                   ` Marcel Holtmann
2003-09-25  3:35                     ` Justin Karneges
2003-09-23 12:49   ` David Woodhouse [this message]

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=1064321387.3793.216.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=justin-qt@affinix.com \
    /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