dri-devel Archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Henry Wu <triangletrap12@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: linux-kbuild@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: A link error related to DRM and fbdev
Date: Wed, 8 May 2024 00:05:38 +0900	[thread overview]
Message-ID: <CAK7LNASSrB_L7VbS1z3O6QuMf0nti1hGJVwip7RRF_-=jn2OHw@mail.gmail.com> (raw)
In-Reply-To: <CAG-UpRQ5Dp4sO2CBTiOpBtjZoRj4U2rNxAwSbari+VcqvayuSQ@mail.gmail.com>

Fw: DRM list

On Mon, May 6, 2024 at 2:53 PM Henry Wu <triangletrap12@gmail.com> wrote:
>
> Hi, all.
>
> I found a link error related to DRM and fbdev on branch linux-5.15.y
> (tag v5.15.157). It has same phenomenon with
> https://lore.kernel.org/all/202303150232.MBonYhiv-lkp@intel.com/.
>
> I tried to investigate this issue and found that build will fail if
> CONFIG_FB=m and it will succeed if CONFIG_FB=y.
>
> [user@localhost linux]$ cat .config | grep
> 'CONFIG_DRM_KMS\|CONFIG_FB\b\|FBDEV_EMUL'
> CONFIG_DRM_KMS_HELPER=y
> CONFIG_DRM_FBDEV_EMULATION=y
> CONFIG_FB=m
> [user@localhost linux]$
>
> I'm not familiar with kbuild. Can anyone troubleshoot it further? You
> can find .config from attachment.


I do not have time to take a look at every build error,
but somebody in the DRM list may help you.



-- 
Best Regards
Masahiro Yamada

       reply	other threads:[~2024-05-07 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG-UpRQ5Dp4sO2CBTiOpBtjZoRj4U2rNxAwSbari+VcqvayuSQ@mail.gmail.com>
2024-05-07 15:05 ` Masahiro Yamada [this message]
2024-05-08  4:01   ` A link error related to DRM and fbdev Henry Wu

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='CAK7LNASSrB_L7VbS1z3O6QuMf0nti1hGJVwip7RRF_-=jn2OHw@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=triangletrap12@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).