From: Michael Schmitz <schmitzmic@gmail.com>
To: Helge Deller <deller@gmx.de>,
linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: Miro Kropacek <miro.kropacek@gmail.com>, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 2/5] fbdev: Give atafb proper parent
Date: Mon, 17 Aug 2026 06:37:02 +1200 [thread overview]
Message-ID: <41ca1d69-9a5e-7f4e-62a8-6f697e87e8f1@gmail.com> (raw)
In-Reply-To: <3d215ce1-6298-491e-81ef-b19bed7f1d9a@gmx.de>
Hi Helge,
no changes to the fbdev patches - just didn't know how else to avoid
issues with b4.
Cheers,
Michael
Am 17.08.2026 um 02:38 schrieb Helge Deller:
> On 8/16/26 09:37, Michael Schmitz wrote:
>> From: Miro Kropacek <miro.kropacek@gmail.com>
>>
>> The atafb fb device registers no parent, causing a missing symlink
>> (/sys/class/graphics/fb0/device). Xorg fbdevhw driver looks for that
>> symlink when scanning for devices, so add a parent node for atafb.
>>
>> Signed-off-by: Miro Kropacek <miro.kropacek@gmail.com>
>> Reviewed-by: Michael Schmitz <schmitzmic@gmail.com>
>> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>
>> Cc: <linux-fbdev@vger.kernel.org>
>> Link: https://lists.debian.org/debian-68k/2026/08/msg00000.html
>
> Did anything on the fbdev patches (#2-#4) changed between v1 and v2?
>
> Helge
>
next prev parent reply other threads:[~2026-08-16 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260816073752.16656-1-schmitzmic@gmail.com>
2026-08-16 7:37 ` [PATCH v2 2/5] fbdev: Give atafb proper parent Michael Schmitz
2026-08-16 14:38 ` Helge Deller
2026-08-16 18:37 ` Michael Schmitz [this message]
2026-08-17 6:34 ` Thomas Zimmermann
2026-08-17 7:49 ` Michael Schmitz
2026-08-17 7:57 ` Thomas Zimmermann
2026-08-16 7:37 ` [PATCH v2 3/5] fbdev: Add support for further video bit depths on atafb:external Michael Schmitz
2026-08-16 7:37 ` [PATCH v2 4/5] fbdev: Add support for SuperVidel's SuperBlitter Michael Schmitz
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=41ca1d69-9a5e-7f4e-62a8-6f697e87e8f1@gmail.com \
--to=schmitzmic@gmail.com \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=miro.kropacek@gmail.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