From: Christoph Hellwig <hch@lst.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: maxk@qualcomm.com, bluez-devel@lists.sourceforge.net
Subject: Re: [PATCH] bluetooth: use kthread_ API
Date: Fri, 14 Jul 2006 10:03:33 +0200 [thread overview]
Message-ID: <20060714080333.GA10043@lst.de> (raw)
In-Reply-To: <1152798551.4838.14.camel@localhost>
On Thu, Jul 13, 2006 at 03:49:11PM +0200, Marcel Holtmann wrote:
> Hi Christoph,
>
> thanks for the patch. It is in my -mh patch now for further testing.
> What about RFCOMM. No fun in touching that one?
Actually I'm pretty sure I had a patch for that aswell. Unfortunately
the box I have the kthread patches on doesn't seem to boot currently.
You'll get the rfcomm patch when I return from Ottawa.
next prev parent reply other threads:[~2006-07-14 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 18:58 [PATCH] bluetooth: use kthread_ API Christoph Hellwig
2006-07-13 13:49 ` [Bluez-devel] " Marcel Holtmann
2006-07-14 8:03 ` Christoph Hellwig [this message]
2006-07-14 9:10 ` Marcel Holtmann
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=20060714080333.GA10043@lst.de \
--to=hch@lst.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.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;
as well as URLs for NNTP newsgroup(s).