From: Philipp Zabel <p.zabel@pengutronix.de>
To: Daniel Vetter <daniel@ffwll.ch>, Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 7 (drivers/gpu/drm/imx/parallel-display.o)
Date: Fri, 08 Jan 2021 11:17:32 +0100 [thread overview]
Message-ID: <8a37aaa3bd4d2b032f45cbab998943e6a7f5c086.camel@pengutronix.de> (raw)
In-Reply-To: <CAKMK7uGP6tmmSx8jFcGK_kLDYQO6PBy-TYMEj=WWh5VRTJ7cFQ@mail.gmail.com>
On Fri, 2021-01-08 at 10:03 +0100, Daniel Vetter wrote:
> On Fri, Jan 8, 2021 at 9:55 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> > On 1/6/21 7:01 PM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20210106:
> > >
> >
> > on x86_64:
> >
> > ld: drivers/gpu/drm/imx/parallel-display.o: in function `imx_pd_connector_get_modes':
> > parallel-display.c:(.text+0x8d): undefined reference to `of_get_drm_display_mode'
>
> Probably something in the pull from philipp that I just merged
> yesterday.
That is likely, although I'm not quite sure how that activated, the
of_get_drm_display_mode call was there before.
> Philip, can you pls take care?
> -Daniel
Thank you for the notice, since the of_get_drm_display_mode() is only
for legacy device trees I'd like to stub it out and keep compile test
coverage:
https://lore.kernel.org/dri-devel/20210108101343.23695-1-p.zabel@pengutronix.de/T/#u
regards
Philipp
prev parent reply other threads:[~2021-01-08 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 3:01 linux-next: Tree for Jan 7 Stephen Rothwell
2021-01-07 17:19 ` linux-next: Tree for Jan 7 (drivers/gpu/drm/imx/parallel-display.o) Randy Dunlap
2021-01-08 9:03 ` Daniel Vetter
2021-01-08 10:17 ` Philipp Zabel [this message]
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=8a37aaa3bd4d2b032f45cbab998943e6a7f5c086.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).