netdev - Re: [PATCHv4] wlcore: add wl1285 compatible

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]

Message-Id: <20170522.103010.1779800840743690143.davem@davemloft.net>
Date:   Mon, 22 May 2017 10:30:10 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     kvalo@...eaurora.org
Cc:     sebastian.reichel@...labora.co.uk, sre@...nel.org,
        tony@...mide.com, marcel@...tmann.org, robh+dt@...nel.org,
        linux-wireless@...r.kernel.org, linux-omap@...r.kernel.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCHv4] wlcore: add wl1285 compatible

From: Kalle Valo <kvalo@...eaurora.org>
Date: Mon, 22 May 2017 12:28:20 +0300

> Sebastian Reichel <sebastian.reichel@...labora.co.uk> writes:
> 
>> Motorola Droid 4 uses a WL1285C. With differences between the
>> chips not being public let's add explicit binding for wl1285
>> instead of relying on wl1283 being very similar.
>>
>> Reviewed-by: Rob Herring <robh@...nel.org>
>> Acked-by: Kalle Valo <kvalo@...eaurora.org>
>> Acked-by: Tony Lindgren <tony@...mide.com>
>> Signed-off-by: Sebastian Reichel <sebastian.reichel@...labora.co.uk>
>> ---
>> Hi Dave,
>>
>> I previously send this in two patches, but its hard to apply without
>> requiring multiple kernel releases (the driver must be updated before
>> the DTS change). Since the actual change is not very complex Marcel
>> Holtmann & Tony Lindgren suggested, that I send this directly to you
>> in a single patch for inclusion into 4.12. This also means, that the
>> remaining series can be queued normally for 4.13.
> 
> I noticed that Dave set this patch to Awaiting Upstream state on his
> patchwork:
> 
> https://patchwork.ozlabs.org/patch/759042/
> 
> Which makes me suspect that he is waiting me to apply this (as I
> normally apply wlcore patches). Dave, should I actually take this patch?
> What do you prefer?

Anything that touches wireless drivers I defer to you, yes.