From: Johan Hedberg <johan.hedberg@gmail.com>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org, padovan@profusion.mobi,
marcel@holtmann.org
Subject: Re: [RESEND PATCH 1/4] Bluetooth: Introduce to_hci_dev()
Date: Thu, 9 Feb 2012 23:24:37 +0200 [thread overview]
Message-ID: <20120209212437.GA453@x220.P-661HNU-F1> (raw)
In-Reply-To: <1328821115-12514-1-git-send-email-dh.herrmann@googlemail.com>
Hi David,
On Thu, Feb 09, 2012, David Herrmann wrote:
> We currently use dev_set_drvdata to keep a pointer to ourself. This
> doesn't make sense as we are the bus and not a driver. Therefore,
> introduce to_hci_dev() so we can get a struct hci_dev pointer from a
> struct device pointer.
>
> dev_set/get_drvdata() is reserved for drivers that provide a device and
> not for the bus using the device. The bus can use simple pointer
> arithmetic to retrieve its private data.
>
> Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
> Acked-by: Marcel Holtmann <marcel@holtmann.org>
> ---
> Acked in: Message-ID: <1327960525.1955.178.camel@aeonflux>
>
> include/net/bluetooth/hci_core.h | 2 ++
> net/bluetooth/hci_sysfs.c | 33 ++++++++++++++++-----------------
> 2 files changed, 18 insertions(+), 17 deletions(-)
Sorry about missing these initially. Last week had plenty of
distractions to offer thanks to the UPF. Anyway, all four patches have
been applied to my bluetooth-next tree now.
Johan
prev parent reply other threads:[~2012-02-09 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 20:58 [RESEND PATCH 1/4] Bluetooth: Introduce to_hci_dev() David Herrmann
2012-02-09 20:58 ` [RESEND PATCH] Bluetooth: btusb: Remove device lock on release David Herrmann
2012-02-09 21:25 ` Johan Hedberg
2012-02-10 5:12 ` Mohanan, Rajmohan
2012-02-09 20:58 ` [RESEND PATCH 2/4] Bluetooth: Remove hci_dev->driver_data David Herrmann
2012-02-09 20:58 ` [RESEND PATCH 3/4] Bluetooth: Introduce to_hci_conn David Herrmann
2012-02-09 20:58 ` [RESEND PATCH 4/4] Bluetooth: Use proper datatypes in release-callbacks David Herrmann
2012-02-09 21:24 ` Johan Hedberg [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=20120209212437.GA453@x220.P-661HNU-F1 \
--to=johan.hedberg@gmail.com \
--cc=dh.herrmann@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
/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