[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YV6EVcKUQj5DNiXZ@kroah.com>
Date: Thu, 7 Oct 2021 07:23:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Zev Weiss <zev@...ilderbeest.net>
Cc: openbmc@...ts.ozlabs.org, Jeremy Kerr <jk@...econstruct.com.au>,
Joel Stanley <joel@....id.au>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Krzysztof WilczyĆski <kw@...ux.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Heiner Kallweit <hkallweit1@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] sysfs: add sysfs_remove_bin_file_self() function
On Wed, Oct 06, 2021 at 05:09:46PM -0700, Zev Weiss wrote:
> This is simply the bin_attribute analog to sysfs_remove_file_self().
No, no binary sysfs file should be triggering a remove.
binary sysfs files are "pass-through-only" from userspace to hardware,
the kernel should not be even knowing what is read/written to them.
What do you think this is needed for?
thanks,
greg k-h
Powered by blists - more mailing lists