From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com,
luiz.von.dentz@intel.com
Cc: marcel@holtmann.org, luiz.dentz@gmail.com
Subject: of btintel_regmap_init
Date: Thu, 3 Oct 2024 17:51:23 +0000 [thread overview]
Message-ID: <Zv7Zm2sq3Jr7yzW0@gallifrey> (raw)
Hi,
A script of mine noticed that btintel_regmap_init doesn't appear
to be called anywhere; it was added way back by:
commit d06f107bcd828a6c3ecd4a7d449d5d0c0dba0326
Author: Loic Poulain <loic.poulain@intel.com>
Date: Thu Oct 1 18:16:21 2015 +0200
Bluetooth: btintel: Add iBT register access over HCI support
and I don't think it's ever been called since.
Is this just dead code (which I'd be happy to prepare a patch to remove)
or should this be called from somewhere?
Dave
P.S. I'm doing general deadcoding here, and don't know much about BT
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
reply other threads:[~2024-10-03 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zv7Zm2sq3Jr7yzW0@gallifrey \
--to=dave@treblig.org \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.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