From: Helge Deller <deller@gmx.de>
To: Shixiong Ou <oushixiong@kylinos.cn>, Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the fbdev tree
Date: Tue, 18 Aug 2026 10:41:55 +0200 [thread overview]
Message-ID: <b0140080-c70c-49f6-98dc-6e1993eda2b3@gmx.de> (raw)
In-Reply-To: <423e330a-31ec-4711-9ac8-0c9c195aba80@kylinos.cn>
Hello Shixiong,
On 8/18/26 08:24, Shixiong Ou wrote:
> Thanks for the quick feedback and for looking into this.
> I just checked the public for-next tree at
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/log/?h=for-next <https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/log/?h=for-next>
> but couldn't spot the fix yet. Has it been pushed, or is it still local?
> If it hasn't been pushed yet, I'm happy to send a formal fix patch to the list.
It's there already:
https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/commit/?h=for-next&id=e36aa3669e0f2981bce9be85d38c50d83bf5e1ff
- goto err_free_fb;
+ return -ENODEV;
Helge
>
> Best regards
> Shixiong.
>
> On 2026/8/15 16:44, Helge Deller wrote:
>> On 8/14/26 18:12, Mark Brown wrote:
>>> After merging the fbdev tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
>>> /tmp/next/build/drivers/video/fbdev/aty/aty128fb.c:2027:6: error:
>>> variable 'info' is used uninitialized whenever 'if' condition is true
>>> [-Werror,-Wsometimes-uninitialized]
>>> 2027 | if (!pcim_request_region(pdev, 2, "aty128fb MMIO")) {
>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> ....
>>> Caused by commit
>>>
>>> 99c188b02c281 (fbdev: aty128fb: Convert to managed PCI and ioremap API)
>> This is fixed now in the fbdev for-next tree.
>>
>> Helge
next prev parent reply other threads:[~2026-08-18 8:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 16:12 Mark Brown
2026-08-15 8:44 ` Helge Deller
[not found] ` <423e330a-31ec-4711-9ac8-0c9c195aba80@kylinos.cn>
2026-08-18 8:41 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-08 23:44 Mark Brown
2024-10-15 1:01 Stephen Rothwell
2024-10-15 7:15 ` Thomas Zimmermann
2024-10-15 8:17 ` Helge Deller
2022-02-16 0:29 Stephen Rothwell
2022-02-16 7:16 ` Helge Deller
2019-06-20 1:41 Stephen Rothwell
2019-06-24 1:45 ` Stephen Rothwell
2019-06-24 4:15 ` Stephen Rothwell
2018-06-29 1:07 Stephen Rothwell
2018-06-29 9:32 ` Hans de Goede
2011-04-07 2:48 Stephen Rothwell
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=b0140080-c70c-49f6-98dc-6e1993eda2b3@gmx.de \
--to=deller@gmx.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=oushixiong@kylinos.cn \
/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
all inboxes | Powered by JetHome®