From: Marcel Holtmann <marcel@holtmann.org>
To: Kartikey Parmar <kartikey2781@gmail.com>
Cc: Oliver Neukum <oliver@neukum.org>,
linux-usb@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: problem in btusb driver for linux-2.6.30
Date: Fri, 11 Sep 2009 10:51:52 +0200 [thread overview]
Message-ID: <1252659112.8931.57.camel@violet> (raw)
In-Reply-To: <6887eb5d0909110137v3ea9849flcd10c17b756fb043@mail.gmail.com>
Hi Kartikey,
first of all, please stop top posting.
> I checked it with 2.6.22, obtained same results.
Second, Oliver asked for 2.6.30 results.
> Kindly find kernel log in the attachment.
Third, we need the lsusb -v or /proc/bus/usb/devices output.
Regards
Marcel
next prev parent reply other threads:[~2009-09-11 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6887eb5d0909102327u2ca531d1q35d027839495a978@mail.gmail.com>
2009-09-11 6:32 ` problem in btusb driver for linux-2.6.30 Oliver Neukum
2009-09-11 8:24 ` Marcel Holtmann
2009-09-11 8:37 ` Kartikey Parmar
2009-09-11 8:51 ` Marcel Holtmann [this message]
2009-09-11 12:14 ` Kartikey Parmar
2009-09-11 13:40 ` 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=1252659112.8931.57.camel@violet \
--to=marcel@holtmann.org \
--cc=kartikey2781@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.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