From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Rob Herring <robh+dt@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@codeaurora.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support
Date: Wed, 3 May 2017 17:19:17 -0700 [thread overview]
Message-ID: <20170504001917.GM3780@atomide.com> (raw)
In-Reply-To: <20170503160827.v5owcbiclea4f7kx@earth>
* Sebastian Reichel <sebastian.reichel@collabora.co.uk> [170503 09:11]:
> Hi,
>
> On Wed, May 03, 2017 at 05:02:13PM +0200, Marcel Holtmann wrote:
> > >> Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This
> > >> fixes the DT file to use correct compatible for the wifi node
> > >> and adds the bluetooth node.
> > >>
> > >> [0] https://www.ifixit.com/Teardown/Motorola+Droid+4+Teardown/7759#s31961
> > >>
> > >> Changes to PATCHv1:
> > >> - use proper compatible value for bluetooth / shared transport
> > >> - add patches fixing wlcore compatible for Droid 4
> > >>
> > >> -- Sebastian
> > >>
> > >> Sebastian Reichel (4):
> > >> wlcore: add wl1285 compatible
> > >> ARM: dts: omap4-droid4: Use wl1285 for wifi compatible
> > >> Bluetooth: hci_ll: Add compatible values for more WL chips
> > >> ARM: dts: omap4-droid4: Add bluetooth
> > >
> > > For the series,
> > >
> > > Reviewed-by: Rob Herring <robh@kernel.org>
> >
> > so now the question is if we merge this through a single
> > maintainer or have each maintainer take the pieces? I would almost
> > suggest that Dave Miller takes this directly into net-next to make
> > this smoother.
>
> I think the only complex thing is, that patch 2 should only be
> applied after patch 1. So maybe patch 1 could be applied via
> wireless/net-next for 4.12 and the other ones go through the
> individual subsystems for 4.13?
Yeah removing dependencies where possible avoids pointless
merge conflicts later on.
Please send patches 1 and 2 together as a single patch to
Dave Miller and describe why it's needed for v4.12. The rest
can then get merged via the BT and DT trees.
Regards,
Tony
prev parent reply other threads:[~2017-05-04 0:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 14:22 [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support Sebastian Reichel
2017-05-03 14:22 ` [PATCHv2 1/4] wlcore: add wl1285 compatible Sebastian Reichel
2017-05-03 14:22 ` [PATCHv2 2/4] ARM: dts: omap4-droid4: Use wl1285 for wifi compatible Sebastian Reichel
2017-05-03 14:22 ` [PATCHv2 3/4] Bluetooth: hci_ll: Add compatible values for more WL chips Sebastian Reichel
2017-05-03 14:22 ` [PATCHv2 4/4] ARM: dts: omap4-droid4: Add bluetooth Sebastian Reichel
2017-05-16 16:41 ` Tony Lindgren
2017-05-03 14:47 ` [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support Rob Herring
2017-05-03 15:02 ` Marcel Holtmann
2017-05-03 16:08 ` Sebastian Reichel
2017-05-04 0:19 ` Tony Lindgren [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=20170504001917.GM3780@atomide.com \
--to=tony@atomide.com \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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).