All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	bluez-devel@lists.sourceforge.net,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Problems with CF bluetooth
Date: Thu, 29 Sep 2005 22:37:07 +0100	[thread overview]
Message-ID: <20050929213707.GH7684@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050929213219.GA2180@elf.ucw.cz>

On Thu, Sep 29, 2005 at 11:32:19PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > I believe it would happen with any other CF card, too. Can you
> > > hciattach it, unplug, hciattach again?
> > 
> > actually I don't have any of them with me and I don't saw a problem with
> > my Casira of a serial port.
> 
> Following patch seems to work around it. And yes, printk() triggers
> twice after 

What's the problem this patch is trying to address?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-09-29 21:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 13:48 Problems with CF bluetooth Pavel Machek
2005-09-29 13:56 ` [Bluez-devel] " Nelson Murilo
2005-09-29 15:45 ` Marcel Holtmann
2005-09-29 15:56   ` Pavel Machek
2005-09-29 16:29     ` Marcel Holtmann
2005-09-29 17:54       ` Pavel Machek
2005-09-29 17:58         ` Marcel Holtmann
2005-09-29 21:32           ` Pavel Machek
2005-09-29 21:37             ` Russell King [this message]
2005-09-29 21:43               ` Pavel Machek
2005-09-29 21:45                 ` Russell King
2005-09-29 21:52                   ` Pavel Machek
2005-09-29 22:01                     ` Russell King
2005-09-29 22:04                       ` Pavel Machek

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=20050929213707.GH7684@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=pavel@ucw.cz \
    /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.