lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 3 May 2017 17:19:17 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Sebastian Reichel <sebastian.reichel@...labora.co.uk>
Cc:     Marcel Holtmann <marcel@...tmann.org>,
        Rob Herring <robh+dt@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Kalle Valo <kvalo@...eaurora.org>,
        "open list:BLUETOOTH DRIVERS" <linux-bluetooth@...r.kernel.org>,
        linux-wireless <linux-wireless@...r.kernel.org>,
        linux-omap <linux-omap@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

* Sebastian Reichel <sebastian.reichel@...labora.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@...nel.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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ