Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Daniel Vetter" <daniel@ffwll.ch>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Bert Karwatzki <spasswolf@web.de>,
	"Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
	intel-gfx@lists.freedesktop.org, "Kurmi,
	Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
	"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Re: [PATCH] fbdev: Introduce devm_register_framebuffer()
Date: Fri, 30 Aug 2024 12:19:08 +0200	[thread overview]
Message-ID: <7aa99a5f-306b-4c9b-88d2-9ea93c013eda@gmx.de> (raw)
In-Reply-To: <729c4f82-a683-4302-b4ae-f591ac04daa1@gmx.de>

On 8/30/24 12:16, Helge Deller wrote:
> On 8/30/24 11:45, Thomas Weißschuh wrote:
>> Introduce a device-managed variant of register_framebuffer() which
>> automatically unregisters the framebuffer on device destruction.
>> This can simplify the error handling and resource management in drivers.
>>
>> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
>> ---
>> This is a fixed resend of [0], which was broken.
>> Thanks to Bert [1], and Chaitanya Kumar [2]
>> for reporting the issue.
>>
>> [0] https://lore.kernel.org/lkml/20240827-efifb-sysfs-v1-3-c9cc3e052180@weissschuh.net/
>> [1] https://lore.kernel.org/lkml/20240829224124.2978-1-spasswolf@web.de/
>> [2] https://lore.kernel.org/lkml/SJ1PR11MB612925C1C533C09F8F62F7CBB9972@SJ1PR11MB6129.namprd11.prod.outlook.com/
>
> I've applied this patch to the fbdev git tree.
> Please double check at
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/log/?h=for-next
>
> Can you please check if this fixes this new report too:
> https://marc.info/?l=linux-fbdev&m=172500784802901&w=2

Please ignore this ^^^.  You already mentioned this one above.
Helge


>> Helge, I didn't document the function devm_unregister_framebuffer() as
>> it is only an internal helper and will ever only used by one user,
>> similar to other helpers in fbmem.c.
>
> Ok.
>
> Helge


  reply	other threads:[~2024-08-30 10:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30  9:45 [PATCH] fbdev: Introduce devm_register_framebuffer() Thomas Weißschuh
2024-08-30 10:16 ` Helge Deller
2024-08-30 10:19   ` Helge Deller [this message]
2024-08-30 10:22   ` Thomas Weißschuh
2024-08-30 10:52 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-08-30 11:00 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-01  2:01 ` ✗ Fi.CI.IGT: failure " Patchwork

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=7aa99a5f-306b-4c9b-88d2-9ea93c013eda@gmx.de \
    --to=deller@gmx.de \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=spasswolf@web.de \
    --cc=suresh.kumar.kurmi@intel.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