From: Marcel Holtmann <marcel@holtmann.org>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Greg K-H <greg@kroah.com>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 0/2] driver core: device_move() fallout.
Date: Tue, 09 Jan 2007 23:58:13 +0100 [thread overview]
Message-ID: <1168383493.7216.1.camel@violet> (raw)
In-Reply-To: <20070108201637.4a39c5d5@gondolin.boeblingen.de.ibm.com>
Hi Greg,
> here are two patches that hopefully make device_move() more universally
> usable:
>
> [1/2] Remove device_is_registered() in device_move().
> [2/2] Allow device_move(dev, NULL).
>
> Patches are against your latest git tree. The code works for me, but
> has not been heavily tested.
I tested it with my patch for the Bluetooth RFCOMM layer and it works
fine. Please make sure that it gets into 2.6.20 as soon as possible,
because the current device_move() is simply broken.
Regards
Marcel
prev parent reply other threads:[~2007-01-09 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 19:16 [Patch 0/2] driver core: device_move() fallout Cornelia Huck
2007-01-09 22:58 ` 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=1168383493.7216.1.camel@violet \
--to=marcel@holtmann.org \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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