From: Helge Deller <deller@gmx.de>
To: sukrut heroorkar <hsukrut3@gmail.com>,
David Hunter <david.hunter.linux@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Bernie Thompson <bernie@plugable.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
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:41:43 +0200 [thread overview]
Message-ID: <edccab86-321b-4e6e-998f-3ce320ee0193@gmx.de> (raw)
In-Reply-To: <CAHCkknrZ-ieNKeg-aj3-NVqgGSk770jJpUpCvn_SuffkPu+ZrQ@mail.gmail.com>
>>> 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.
Helge
next prev parent reply other threads:[~2025-10-02 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250924175743.6790-1-hsukrut3@gmail.com>
2025-09-27 16:12 ` [PATCH] fbdev: udlfb: make CONFIG_FB_DEVICE optional kernel test robot
2025-09-28 23:29 ` David Hunter
2025-10-02 6:35 ` sukrut heroorkar
2025-10-02 6:41 ` Helge Deller [this message]
2025-10-02 6:52 ` Thomas Zimmermann
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=edccab86-321b-4e6e-998f-3ce320ee0193@gmx.de \
--to=deller@gmx.de \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=bernie@plugable.com \
--cc=david.hunter.linux@gmail.com \
--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 \
--cc=tzimmermann@suse.de \
/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