public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Brian Rogers <brian@xyzw.org>
Cc: linux-bluetooth@vger.kernel.org,
	Kay Sievers <kay.sievers@vrfy.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Wait for child devices to go away before deleting a connection
Date: Thu, 30 Jul 2009 04:33:11 +0200	[thread overview]
Message-ID: <1248921191.28545.251.camel@violet> (raw)
In-Reply-To: <4A70CF45.1060706@xyzw.org>

Hi Brian,

> >>> Kay, David, wouldn't be pinning of the parent device here be enough to
> >>> get this done in a clean way?
> >>>   
> >>>       
> >> If there's a way that the connection can be pinned until the child 
> >> devices go away, that definitely sounds cleaner to me.
> >>     
> >
> > so I pushed some patches to bluetooth-testing tree that should fix this
> > problem. They are not fully tested by me. Please test and report back
> > the results.
> >   
> 
> Fails to compile if CONFIG_USB_HIDDEV=y :
> 
> ERROR: "hiddev_disconnect" [net/bluetooth/hidp/hidp.ko] undefined!
> 
> Ironically, the reference to hiddev_disconnect is fine if hiddev isn't 
> enabled because then hiddev.h supplies an empty static inline function.
> 
> I'm going to test with a kernel without hiddev for now.

just take that piece out of the patch. It is not important. I just wanna
now if the uevents are now coming in order.

Regards

Marcel



  reply	other threads:[~2009-07-30  2:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  8:03 [PATCH] Wait for child devices to go away before deleting a connection Brian Rogers
2009-07-20  8:10 ` Marcel Holtmann
2009-07-23 13:25   ` Brian Rogers
2009-07-29 21:12     ` Marcel Holtmann
2009-07-29 22:37       ` Brian Rogers
2009-07-30  2:33         ` Marcel Holtmann [this message]
2009-07-30  3:25           ` Brian Rogers
2009-07-30  3:49             ` Marcel Holtmann
2009-07-30  5:24               ` Brian Rogers

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=1248921191.28545.251.camel@violet \
    --to=marcel@holtmann.org \
    --cc=brian@xyzw.org \
    --cc=dwmw2@infradead.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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