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>] [day] [month] [year] [list]
Date:   Tue, 26 Nov 2019 17:34:56 +0100
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Kalle Valo <kvalo@...eaurora.org>
Cc:     Ulf Hansson <ulf.hansson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Alexios Zavras <alexios.zavras@...el.com>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        letux-kernel@...nphoenux.org, kernel@...a-handheld.com
Subject: Re: [PATCH 0/2] net: wireless: ti: wl1251: sdio: remove ti,power-gpio


> Am 26.11.2019 um 16:51 schrieb Kalle Valo <kvalo@...eaurora.org>:
> 
> "H. Nikolaus Schaller" <hns@...delico.com> writes:
> 
>> The driver has been updated to use the mmc/sdio core
>> which does full power control. So we do no longer need
>> the power control gipo.
>> 
>> Note that it is still needed for the SPI based interface
>> (N900).
>> 
>> Suggested by: Ulf Hansson <ulf.hansson@...aro.org>
>> Tested by: H. Nikolaus Schaller <hns@...delico.com> # OpenPandora 600MHz
>> 
>> H. Nikolaus Schaller (2):
>>  DTS: bindings: wl1251: mark ti,power-gpio as optional
>>  net: wireless: ti: wl1251: sdio: remove ti,power-gpio
>> 
>> .../bindings/net/wireless/ti,wl1251.txt       |  3 +-
>> drivers/net/wireless/ti/wl1251/sdio.c         | 30 -------------------
>> 2 files changed, 2 insertions(+), 31 deletions(-)
> 
> Via which tree are these planned to go? Please always document that in
> the cover letter so that maintainers don't need to guess.

Well, how should I know that better than maintainers?

I don't know who manages which trees and who feels responsible.
So I have to guess even more.

I just use the get_maintainer.pl script to address everybody listed by it,
assuming that it does the right thing.

If the script doesn't do a good enough job it should be improved.

BR and thanks,
Nikolaus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ