linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Sebastian Reichel <sre@kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	Tony Lindgren <tony@atomide.com>
Cc: Adam Ford <aford173@gmail.com>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	linux-bluetooth@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: [PATCHv2 0/4] Convert all btwilink users to hci_ll and drop btwilink
Date: Thu,  3 Oct 2019 15:41:43 +0200	[thread overview]
Message-ID: <20191003134147.9458-1-sre@kernel.org> (raw)

Hi,

This moves the remaining users of btwilink to the "new" serdev based hci_ll
driver and drops the btwilink driver afterwards. The patches were only compile
tested by me, but Enric tested the IGEP platform and Adam will test the LogicPD
platform.

I kept the TI_ST driver for now, since I plan to send a second patchset for the
FM radio driver. Once the FM driver has been converted to also use hci_ll, we
can remove TI_ST completly.

My suggestion is for the patch handling is, that everything simply goes through
Tony's tree.

Changes since PATCHv1 [0]
 * rebase to 5.4-rc1
 * move FM radio patches into separate patchset

[0] https://lore.kernel.org/lkml/20181221011752.25627-1-sre@kernel.org/

-- Sebastian

Sebastian Reichel (4):
  ARM: dts: LogicPD Torpedo: Add WiLink UART node
  ARM: dts: IGEP: Add WiLink UART node
  ARM: OMAP2+: pdata-quirks: drop TI_ST/KIM support
  Bluetooth: btwilink: drop superseded driver

 .../boot/dts/logicpd-torpedo-37xx-devkit.dts  |   8 +
 arch/arm/boot/dts/omap3-igep0020-rev-f.dts    |   8 +
 arch/arm/boot/dts/omap3-igep0030-rev-g.dts    |   8 +
 arch/arm/mach-omap2/pdata-quirks.c            |  52 ---
 drivers/bluetooth/Kconfig                     |  11 -
 drivers/bluetooth/Makefile                    |   1 -
 drivers/bluetooth/btwilink.c                  | 337 ------------------
 7 files changed, 24 insertions(+), 401 deletions(-)
 delete mode 100644 drivers/bluetooth/btwilink.c

-- 
2.23.0


             reply	other threads:[~2019-10-03 13:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 13:41 Sebastian Reichel [this message]
2019-10-03 13:41 ` [PATCHv2 1/4] ARM: dts: LogicPD Torpedo: Add WiLink UART node Sebastian Reichel
2019-10-03 21:40   ` Adam Ford
2019-10-03 13:41 ` [PATCHv2 2/4] ARM: dts: IGEP: " Sebastian Reichel
2019-10-03 13:41 ` [PATCHv2 3/4] ARM: OMAP2+: pdata-quirks: drop TI_ST/KIM support Sebastian Reichel
2019-10-03 13:41 ` [PATCHv2 4/4] Bluetooth: btwilink: drop superseded driver Sebastian Reichel
2019-10-16 19:15   ` Marcel Holtmann
2019-10-20 20:59     ` Sebastian Reichel
2019-10-21 15:14       ` Marcel Holtmann
2019-10-23 12:27         ` Sebastian Reichel
2019-10-23 12:42           ` Marcel Holtmann
2019-10-08 14:31 ` [PATCHv2 0/4] Convert all btwilink users to hci_ll and drop btwilink Tony Lindgren
2019-10-20 20:33   ` Sebastian Reichel
2019-10-22 16:01     ` Tony Lindgren
2019-10-23 12:06       ` Sebastian Reichel

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=20191003134147.9458-1-sre@kernel.org \
    --to=sre@kernel.org \
    --cc=aford173@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).