All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Fix dmesg errors about hid2hci not claiming interface before usage.
Date: Sat, 16 May 2009 06:38:44 -0700	[thread overview]
Message-ID: <1242481124.3446.36.camel@localhost.localdomain> (raw)
In-Reply-To: <4A0DFB63.8060006@dell.com>

Hi Mario,

> These errors were caused from trying to detach the kernel driver from
>  the interface, which was unnecessary.  A simple usb_claim_interface
>  is all that is necessary.  It is however, important to ensure the
>  interface claim is successful.
> 
> ---
>  tools/hid2hci.c |   12 ++++--------
>  1 files changed, 4 insertions(+), 8 deletions(-)

patch has been applied. Again, please line-break your commit messages
properly.

Regards

Marcel



      reply	other threads:[~2009-05-16 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 23:31 [PATCH] Fix dmesg errors about hid2hci not claiming interface before usage Mario Limonciello
2009-05-16 13:38 ` Marcel Holtmann [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=1242481124.3446.36.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mario_limonciello@dell.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 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.