From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Harshit Shaw <shawharshit116@gmail.com>
Cc: gregkh@linuxfoundation.org, error27@gmail.com, deller@gmx.de,
chintanlike@gmail.com, tzimmermann@suse.de,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: fbtft: convert sysfs attributes to use ATTRIBUTE_GROUPS
Date: Tue, 12 May 2026 22:16:10 +0300 [thread overview]
Message-ID: <agN8et6OW183t5TH@ashevche-desk.local> (raw)
In-Reply-To: <20260512183007.14511-1-shawharshit116@gmail.com>
On Tue, May 12, 2026 at 06:30:06PM +0000, Harshit Shaw wrote:
> Replace direct device_create_file() calls with the correct
> ATTRIBUTE_GROUPS() macro. Add fbtft_groups as dev_groups in the
> driver structure so the driver core automatically adds and removes
> the sysfs attributes when a device is bound or unbound.
> Signed-off-by: Harshit Shaw <shawharshit116@gmail.com>
> ---
> v2: - Use DEVICE_ATTR_RW() macro instead of DEVICE_ATTR()
> - Move DEVICE_ATTR_RW() definitions closer to their callbacks
> - Remove trailing comma after NULL in attribute array
> - Remove extern declaration from internal.h, not needed
> - Use ATTRIBUTE_GROUPS() macro and add dev_groups to driver
> structure as suggested by Greg KH and Andy Shevchenko
> - Compile tested with: make M=drivers/staging/fbtft modules
Thanks for the update!
...
> +static struct attribute *fbtft_attrs[] = {
>
Now it has stray blank line here.
> + &dev_attr_debug.attr,
> + &dev_attr_gamma.attr,
> + NULL
> +};
...
Otherwise LGTM, and if Sashiko and others are happy with it
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-05-12 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 18:30 [PATCH v2] staging: fbtft: convert sysfs attributes to use ATTRIBUTE_GROUPS Harshit Shaw
2026-05-12 19:16 ` Andy Shevchenko [this message]
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=agN8et6OW183t5TH@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=chintanlike@gmail.com \
--cc=deller@gmx.de \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=shawharshit116@gmail.com \
--cc=tzimmermann@suse.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