linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Helge Deller <deller@gmx.de>,
	sukrut heroorkar <hsukrut3@gmail.com>,
	David Hunter <david.hunter.linux@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
	Bernie Thompson <bernie@plugable.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Randy Dunlap <rdunlap@infradead.org>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Zsolt Kajtar <soci@c64.rulez.org>,
	Gonzalo Silvalde Blanco <gonzalo.silvalde@gmail.com>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	oe-kbuild-all@lists.linux.dev, skhan@linuxfoundation.org
Subject: Re: [PATCH] fbdev: udlfb: make CONFIG_FB_DEVICE optional
Date: Thu, 2 Oct 2025 08:52:17 +0200	[thread overview]
Message-ID: <41ef536d-2399-43f8-8041-c6b0e642aba2@suse.de> (raw)
In-Reply-To: <edccab86-321b-4e6e-998f-3ce320ee0193@gmx.de>

Hi

Am 02.10.25 um 08:41 schrieb Helge Deller:
>>>> kernel test robot noticed the following build errors:
>>>
>>> Did you compile and test this code before submitting this patch?
>>
>> Yes, I had compiled & loaded the udlfb module with no errors. Please
>> let me know how to proceed in this case.
>
> Look at the reported build error, which seems to happen in dev_dbg().
> So, maybe in your testing you did not have debugging enabled?
> The report contains the .config file with which you can test.

Can we rather make an effort to remove the udlfb driver entirely? A few 
years back, there was one user who was still using it because of some 
problems with the DRM udl driver. But I think we've addressed them. The 
discussion is at [1].

[1] 
https://lore.kernel.org/dri-devel/20201130125200.10416-1-tzimmermann@suse.de/

Best regards
Thomas

>
> Helge

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)



  reply	other threads:[~2025-10-02  6:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 17:57 [PATCH] fbdev: udlfb: make CONFIG_FB_DEVICE optional Sukrut Heroorkar
2025-09-26 20:58 ` kernel test robot
2025-09-27 16:12 ` kernel test robot
2025-09-28 23:29   ` David Hunter
2025-10-02  6:35     ` sukrut heroorkar
2025-10-02  6:41       ` Helge Deller
2025-10-02  6:52         ` Thomas Zimmermann [this message]
2025-10-03 18:43           ` sukrut heroorkar
2025-10-03 19:50             ` Helge Deller
2025-10-07  7:35               ` Thomas Zimmermann
2025-10-10 15:11                 ` Mikulas Patocka
2025-10-06 13:49       ` David Hunter

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=41ef536d-2399-43f8-8041-c6b0e642aba2@suse.de \
    --to=tzimmermann@suse.de \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bernie@plugable.com \
    --cc=david.hunter.linux@gmail.com \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gonzalo.silvalde@gmail.com \
    --cc=hsukrut3@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=soci@c64.rulez.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).