diff for duplicates of <20170504001917.GM3780@atomide.com> diff --git a/a/1.txt b/N1/1.txt index cabac22..c63c21a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,35 +1,34 @@ * Sebastian Reichel <sebastian.reichel@collabora.co.uk> [170503 09:11]: > Hi, ->=20 +> > 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. -> > >>=20 -> > >> [0] https://www.ifixit.com/Teardown/Motorola+Droid+4+Teardown/7759#s= -31961 -> > >>=20 +> > >> +> > >> [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 -> > >>=20 +> > >> > > >> -- Sebastian -> > >>=20 +> > >> > > >> 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 -> > >=20 +> > > > > > For the series, -> > >=20 +> > > > > > Reviewed-by: Rob Herring <robh@kernel.org> -> >=20 +> > > > 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. ->=20 +> > 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 diff --git a/a/content_digest b/N1/content_digest index 8130285..6433e04 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -18,36 +18,35 @@ "b\0" "* Sebastian Reichel <sebastian.reichel@collabora.co.uk> [170503 09:11]:\n" "> Hi,\n" - ">=20\n" + "> \n" "> On Wed, May 03, 2017 at 05:02:13PM +0200, Marcel Holtmann wrote:\n" "> > >> Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This\n" "> > >> fixes the DT file to use correct compatible for the wifi node\n" "> > >> and adds the bluetooth node.\n" - "> > >>=20\n" - "> > >> [0] https://www.ifixit.com/Teardown/Motorola+Droid+4+Teardown/7759#s=\n" - "31961\n" - "> > >>=20\n" + "> > >> \n" + "> > >> [0] https://www.ifixit.com/Teardown/Motorola+Droid+4+Teardown/7759#s31961\n" + "> > >> \n" "> > >> Changes to PATCHv1:\n" "> > >> - use proper compatible value for bluetooth / shared transport\n" "> > >> - add patches fixing wlcore compatible for Droid 4\n" - "> > >>=20\n" + "> > >> \n" "> > >> -- Sebastian\n" - "> > >>=20\n" + "> > >> \n" "> > >> Sebastian Reichel (4):\n" "> > >> wlcore: add wl1285 compatible\n" "> > >> ARM: dts: omap4-droid4: Use wl1285 for wifi compatible\n" "> > >> Bluetooth: hci_ll: Add compatible values for more WL chips\n" "> > >> ARM: dts: omap4-droid4: Add bluetooth\n" - "> > >=20\n" + "> > > \n" "> > > For the series,\n" - "> > >=20\n" + "> > > \n" "> > > Reviewed-by: Rob Herring <robh@kernel.org>\n" - "> >=20\n" + "> > \n" "> > so now the question is if we merge this through a single\n" "> > maintainer or have each maintainer take the pieces? I would almost\n" "> > suggest that Dave Miller takes this directly into net-next to make\n" "> > this smoother.\n" - ">=20\n" + "> \n" "> I think the only complex thing is, that patch 2 should only be\n" "> applied after patch 1. So maybe patch 1 could be applied via\n" "> wireless/net-next for 4.12 and the other ones go through the\n" @@ -64,4 +63,4 @@ "\n" Tony -2e0ae958d7c81352d216f865858244814cd36f3a5abcf72dbc2bedb7552af866 +c2c200e4e020a027f6dc4a2c130989ed3df12e39266b1a9103fc6f8090c1d5e2
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.