From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] apply rfcomm oops fix?
Date: Tue, 17 Jul 2007 23:12:53 +0300 [thread overview]
Message-ID: <20070717201253.GH1376@nalle> (raw)
In-Reply-To: <1184702133.28210.38.camel@aeonflux.holtmann.net>
On Tue, Jul 17, 2007 at 09:55:33PM +0200, Marcel Holtmann wrote:
> Hi Mikko,
>
> > This bugzilla entry http://bugzilla.kernel.org/show_bug.cgi?id=7509 has
> > been open for a while and my fix proposal this. I think it makes sence
> > for rfcomm socket ioctl, which releases the device, to gracefully
> > (tty_v)hangup the tty layer too. Could this be applied or is there some
> > problem with this one liner?
>
> check the upstream kernel source. Your patch has already been applied.
Eh, I did and saw a latest patch to net/bluetooth dated in May, but now
a browser reload shows the latest changes made in July. Must be a
gitweb thing...
-Mikko
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-17 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 19:16 [Bluez-devel] apply rfcomm oops fix? Mikko Rapeli
2007-07-17 19:55 ` Marcel Holtmann
2007-07-17 20:12 ` Mikko Rapeli [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=20070717201253.GH1376@nalle \
--to=mikko.rapeli@iki.fi \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.