From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marek Vasut <marex@denx.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/22] Input: ili210x - use device core to create driver-specific device attributes
Date: Sun, 30 Jul 2023 13:38:30 +0200 [thread overview]
Message-ID: <2023073010-debunk-tripping-270a@gregkh> (raw)
In-Reply-To: <fd975ac8-bea4-22ae-cb5f-cbdaa3566d25@denx.de>
On Sat, Jul 29, 2023 at 05:07:17PM +0200, Marek Vasut wrote:
> On 7/29/23 02:51, Dmitry Torokhov wrote:
> > Instead of creating driver-specific device attributes with
> > devm_device_add_group() have device core do this by setting up dev_groups
> > pointer in the driver structure.
> >
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> > drivers/input/touchscreen/ili210x.c | 15 +++++----------
> > 1 file changed, 5 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/input/touchscreen/ili210x.c b/drivers/input/touchscreen/ili210x.c
> > index ad6828e4f2e2..31ffdc2a93f3 100644
> > --- a/drivers/input/touchscreen/ili210x.c
> > +++ b/drivers/input/touchscreen/ili210x.c
> > @@ -876,7 +876,7 @@ static ssize_t ili210x_firmware_update_store(struct device *dev,
> > static DEVICE_ATTR(firmware_update, 0200, NULL, ili210x_firmware_update_store);
> > -static struct attribute *ili210x_attributes[] = {
> > +static struct attribute *ili210x_attrs[] = {
> > &dev_attr_calibrate.attr,
> > &dev_attr_firmware_update.attr,
> > &dev_attr_firmware_version.attr,
> > @@ -904,10 +904,11 @@ static umode_t ili210x_attributes_visible(struct kobject *kobj,
> > return attr->mode;
> > }
> > -static const struct attribute_group ili210x_attr_group = {
> > - .attrs = ili210x_attributes,
> > +static const struct attribute_group ili210x_group = {
> > + .attrs = ili210x_attrs,
>
> Is all the renaming really necessary and relevant to this patch ?
Yes, it's needed for the __ATTRIBUTE_GROUPS() macro.
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-30 11:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 0:51 [PATCH 01/22] Input: cros_ec_keyb - use device core to create driver-specific device attributes Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 02/22] Input: cyapa " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 03/22] Input: iqs269a " Dmitry Torokhov
2023-07-31 15:41 ` Jeff LaBundy
2023-08-02 13:01 ` Mattijs Korpershoek
2023-07-29 0:51 ` [PATCH 04/22] Input: kxtj9 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 05/22] Input: ad7877 " Dmitry Torokhov
2023-07-31 5:23 ` Hennerich, Michael
2023-07-29 0:51 ` [PATCH 06/22] Input: ad7879 " Dmitry Torokhov
2023-07-31 5:23 ` Hennerich, Michael
2023-07-29 0:51 ` [PATCH 07/22] Input: ads7846 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 08/22] Input: edt-ft5x06 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 09/22] Input: elants_i2c " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 10/22] Input: exc3000 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 11/22] Input: hideep " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 12/22] Input: hycon-hy46xx " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 13/22] Input: ili210x " Dmitry Torokhov
2023-07-29 15:07 ` Marek Vasut
2023-07-30 11:38 ` Greg Kroah-Hartman [this message]
2023-07-30 12:24 ` Marek Vasut
2023-07-29 0:51 ` [PATCH 14/22] Input: ilitek_ts_i2c " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 15/22] Input: iqs5xx " Dmitry Torokhov
2023-07-31 15:43 ` Jeff LaBundy
2023-07-29 0:51 ` [PATCH 16/22] Input: melfas-mip4 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 17/22] Input: raydium_i2c_ts " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 18/22] Input: rohm_bu21023 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 19/22] Input: s6sy761 " Dmitry Torokhov
2023-07-30 13:02 ` Andi Shyti
2023-07-29 0:51 ` [PATCH 20/22] Input: stmfts " Dmitry Torokhov
2023-07-30 13:02 ` Andi Shyti
2023-07-29 0:51 ` [PATCH 21/22] Input: tsc2004/5 " Dmitry Torokhov
2023-07-29 0:51 ` [PATCH 22/22] Input: wdt87xx_i2c " Dmitry Torokhov
2023-07-29 2:40 ` [PATCH 01/22] Input: cros_ec_keyb " Guenter Roeck
2023-07-30 11:39 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023073010-debunk-tripping-270a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).