From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: udlfb: remove sysfs framebuffer device with USB .disconnect()
Date: Fri, 27 Jan 2012 16:32:23 +0000 [thread overview]
Message-ID: <CAPXgP10eUncJTOY7Sc82fP3hfbxnFG8BhNWyN26BY+CFha8MGQ@mail.gmail.com> (raw)
In-Reply-To: <1327090686.1555.2.camel@mop>
On Sat, Jan 21, 2012 at 15:32, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Sat, 2012-01-21 at 14:13 +0000, Florian Tobias Schandinat wrote:
>> On 01/21/2012 01:57 PM, Kay Sievers wrote:
>
>> > That's true. If one calls the current _unregister() *before* calling
>> > _unlink(), the _unlink() is a NOP. But that's intentional.
>>
>> I don't think you got me right. My complaint was that after your patch
>> do_unregister_framebuffer itself calls unlink_framebuffer _after_ it set
>> registered_fb[i] = NULL;
>> So for any framebuffer that does not call unlink_framebuffer directly the line
>> device_destroy(fb_class, MKDEV(FB_MAJOR, i));
>> will no longer be executed. Do you agree?
>
> Yes, I absolutely agree. :)
Hey Florian,
any updates?
We like to get that into the Fedora kernel, as we promised
out-of-the-box multi-seat hotplug support, but the framebuffer events
are broken at the moment.
It would be nice if it would show up in -next somehow, and gets
testing, so I don't need to convince anybody at the Fedora kernel
side, that this will land upstream ...
Thanks,
Kay
next prev parent reply other threads:[~2012-01-27 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 20:18 udlfb: remove sysfs framebuffer device with USB .disconnect() Kay Sievers
2012-01-21 13:44 ` Florian Tobias Schandinat
2012-01-21 13:57 ` Kay Sievers
2012-01-21 14:13 ` Florian Tobias Schandinat
2012-01-21 14:32 ` Kay Sievers
2012-01-27 16:32 ` Kay Sievers [this message]
2012-01-30 5:16 ` Florian Tobias Schandinat
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=CAPXgP10eUncJTOY7Sc82fP3hfbxnFG8BhNWyN26BY+CFha8MGQ@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-fbdev@vger.kernel.org \
/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).