linux-kernel - Re: [PATCH 3/3] Documentation: ABI: sysfs-driver-regulator-output

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2023092037-denote-enslave-0a3f@gregkh>
Date:   Wed, 20 Sep 2023 11:29:15 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Zev Weiss <zev@...ilderbeest.net>
Cc:     Mark Brown <broonie@...nel.org>,
        Naresh Solanki <naresh.solanki@...ements.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Documentation: ABI: sysfs-driver-regulator-output

On Wed, Sep 20, 2023 at 02:02:49AM -0700, Zev Weiss wrote:
>  static int regulator_userspace_notify(struct notifier_block *nb,
>  				      unsigned long event,
>  				      void *ignored)
>  {
>  	struct userspace_consumer_data *data =
>  		container_of(nb, struct userspace_consumer_data, nb);
> -	static const char * const *envp[] = { "NAME=events", NULL };

You removed this user/kernel api value, what will break if you do that?

thanks,

greg k-h