From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
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: Re: [PATCHv2 0/4] Convert all btwilink users to hci_ll and drop btwilink
Date: Tue, 22 Oct 2019 09:01:11 -0700 [thread overview]
Message-ID: <20191022160111.GP5610@atomide.com> (raw)
In-Reply-To: <20191020203352.rh3n6qpagiyift7d@earth.universe>
* Sebastian Reichel <sre@kernel.org> [191020 20:34]:
> Hi Tony,
>
> On Tue, Oct 08, 2019 at 07:31:16AM -0700, Tony Lindgren wrote:
> > * Sebastian Reichel <sre@kernel.org> [191003 06:42]:
> > > 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.
> >
> > Sounds good to me, good to see kim gone with patch 3/4 :)
> >
> > Marcel, care to ack the old driver removal patch?
>
> Looks like Marcel missed the extra messages and merged the 4th
> patch, so I guess you can just merge patches 1-3. Technically that
> might lead to temporarily missing BT support on those two devices
> when the BT tree is merged before ARM tree during the merge window.
> Not a big issue I guess.
Sure no problem. Applying dts changes into omap-for-v5.5/dt
and the pdata quirk removal to omap-for-v5.5/soc.
I guess ti_wilink_st.h will need some follow-up patch to
remove unused platform data, but best to wait on that.
Regards,
Tony
next prev parent reply other threads:[~2019-10-22 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 13:41 [PATCHv2 0/4] Convert all btwilink users to hci_ll and drop btwilink Sebastian Reichel
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 [this message]
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=20191022160111.GP5610@atomide.com \
--to=tony@atomide.com \
--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=sre@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;
as well as URLs for NNTP newsgroup(s).