netdev - Re: [PATCH v9 01/24] mmc: sdio: add SDIO IDs for Silabs WF200 chip

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: <87k0f5t95y.fsf@kernel.org>
Date:   Wed, 12 Jan 2022 14:45:13 +0200
From:   Kalle Valo <kvalo@...nel.org>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     Jerome Pouiller <Jerome.Pouiller@...abs.com>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "David S . Miller" <davem@...emloft.net>,
        devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        linux-mmc@...r.kernel.org,
        Pali Rohár <pali@...nel.org>
Subject: Re: [PATCH v9 01/24] mmc: sdio: add SDIO IDs for Silabs WF200 chip

Ulf Hansson <ulf.hansson@...aro.org> writes:

> On Tue, 11 Jan 2022 at 18:14, Jerome Pouiller
> <Jerome.Pouiller@...abs.com> wrote:
>>
>> From: Jérôme Pouiller <jerome.pouiller@...abs.com>
>>
>> Note that the values used by Silabs are uncommon. A driver cannot fully
>> rely on the SDIO PnP. It should also check if the device is declared in
>> the DT.
>>
>> So, to apply the quirks necessary for the Silabs WF200, we rely on the
>> DT rather than on the SDIO VID/PID.
>>
>> Signed-off-by: Jérôme Pouiller <jerome.pouiller@...abs.com>
>
> I guess the series is getting close to getting queued up?
>
> As an option to make sure $subject patch doesn't cause a problem for
> that, I can queue it up and send it for the 5.17-rcs or if Kalle
> prefer to carry this in this tree with my ack?
>
> Kalle?

The easiest is if you can take it to your tree, tack!

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches