linux-kernel - Re: [PATCH v2] pwm: Use device_get_match

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] [day] [month] [year] [list]

Message-ID: <170119076371.215216.199281430371759022.b4-ty@gmail.com>
Date:   Tue, 28 Nov 2023 17:59:55 +0100
From:   Thierry Reding <thierry.reding@...il.com>
To:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>, Heiko Stuebner <heiko@...ech.de>,
        Rob Herring <robh@...nel.org>
Cc:     linux-pwm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org,
        linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH v2] pwm: Use device_get_match_data()


On Thu, 26 Oct 2023 14:54:17 -0500, Rob Herring wrote:
> Use preferred device_get_match_data() instead of of_match_device() to
> get the driver match data. With this, adjust the includes to explicitly
> include the correct headers.
> 
> As these drivers only do DT based matching, of_match_device() will never
> return NULL if we've gotten to probe(). Therefore, the NULL check and
> error returns can be dropped.
> 
> [...]

Applied, thanks!

[1/1] pwm: Use device_get_match_data()
      commit: cf5a1a8c8e8875b3fe38835942b393cc1577da55

Best regards,
-- 
Thierry Reding <thierry.reding@...il.com>