Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: oushixiong1025@163.com
Cc: "Thomas Zimmermann" <tzimmermann@suse.de>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	"Lee Jones" <lee@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	"Shixiong Ou" <oushixiong@kylinos.cn>
Subject: Re: [PATCH] fbdev: lcdcfb: Register sysfs groups through driver core
Date: Sun, 9 Mar 2025 03:00:35 +0100	[thread overview]
Message-ID: <e88f483c-1439-40f2-8945-dfa4de373153@gmx.de> (raw)
In-Reply-To: <20250219084427.244985-1-oushixiong1025@163.com>

On 2/19/25 09:44, oushixiong1025@163.com wrote:
> From: Shixiong Ou <oushixiong@kylinos.cn>
>
> [WHY]
>     1. The driver forgot to call device_remove_file()
>     in sh_mobile_lcdc_overlay_fb_unregister(), and there was
>     no error handling when calling device_create_file() failed.
>
>     2. This should probably use device_add_group() instead of
>     individual files to simplify both creation and removal. [Arnd]
>
>     3. The driver core can register and cleanup sysfs groups already.
>     as commit 95cdd538e0e5 ("fbdev: efifb: Register sysfs groups
>     through driver core").
>
> [HOW]
>     Register sysfs groups through driver core.
>
> Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>
> ---
>   drivers/video/fbdev/sh_mobile_lcdcfb.c | 29 ++++++++++++--------------
>   1 file changed, 13 insertions(+), 16 deletions(-)

applied.

Thanks!
Helge

      reply	other threads:[~2025-03-09  2:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19  8:44 [PATCH] fbdev: lcdcfb: Register sysfs groups through driver core oushixiong1025
2025-03-09  2:00 ` Helge Deller [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=e88f483c-1439-40f2-8945-dfa4de373153@gmx.de \
    --to=deller@gmx.de \
    --cc=arnd@arndb.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=lee@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oushixiong1025@163.com \
    --cc=oushixiong@kylinos.cn \
    --cc=tzimmermann@suse.de \
    --cc=u.kleine-koenig@baylibre.com \
    /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