[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024041128-huddling-humped-4304@gregkh>
Date: Thu, 11 Apr 2024 15:07:46 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Lukas Wunner <lukas@...ner.de>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, linux-kernel@...r.kernel.org,
Michael Ellerman <mpe@...erman.id.au>,
linuxppc-dev@...ts.ozlabs.org, linux-acpi@...r.kernel.org,
Jean Delvare <jdelvare@...e.com>, Ard Biesheuvel <ardb@...nel.org>,
linux-efi@...r.kernel.org, Zhenyu Wang <zhenyuw@...ux.intel.com>,
Zhi Wang <zhi.wang.linux@...il.com>,
intel-gvt-dev@...ts.freedesktop.org,
Daniel Lezcano <daniel.lezcano@...aro.org>,
linux-pm@...r.kernel.org, Luis Chamberlain <mcgrof@...nel.org>,
linux-modules@...r.kernel.org
Subject: Re: [PATCH 0/2] Deduplicate bin_attribute simple read() callbacks
On Sat, Apr 06, 2024 at 03:52:00PM +0200, Lukas Wunner wrote:
> For my upcoming PCI device authentication v2 patches, I have the need
> to expose a simple buffer in virtual memory as a bin_attribute.
>
> It turns out we've duplicated the ->read() callback for such simple
> buffers a fair number of times across the tree.
>
> So instead of reinventing the wheel, I decided to introduce a common
> helper and eliminate all duplications I could find.
>
> I'm open to a bikeshedding discussion on the sysfs_bin_attr_simple_read()
> name. ;)
Seems like no one objects, should I just take this through my
driver-core tree for 6.10?
thanks,
greg k-h
Powered by blists - more mailing lists