From: Lyude Paul <lyude@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Guenter Roeck <linux@roeck-us.net>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>, Sean Paul <sean@poorly.run>,
David Airlie <airlied@linux.ie>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/dp_mst: Fix build on systems with STACKTRACE_SUPPORT=n
Date: Tue, 03 Dec 2019 16:30:34 -0500 [thread overview]
Message-ID: <b35216fce6ed8f822d9147b2fa96a7cd840d96a9.camel@redhat.com> (raw)
In-Reply-To: <20191203093334.GB624164@phenom.ffwll.local>
On Tue, 2019-12-03 at 10:33 +0100, Daniel Vetter wrote:
> On Mon, Dec 02, 2019 at 01:49:47PM -0500, Lyude Paul wrote:
> > Reviewed-by: Lyude Paul <lyude@redhat.com>
> >
> > I'll go ahead and push this to drm-misc-next, thanks!
>
> drm-misc-next-fixes since it's in the merge window. drm-misc-next is for
> 5.6 already.
> -Daniel
Ahh, that explains things :). Pushed, thanks for the patches!
>
> > On Mon, 2019-12-02 at 16:20 +0100, Geert Uytterhoeven wrote:
> > > On Mon, Dec 2, 2019 at 2:41 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > > > On systems with STACKTRACE_SUPPORT=n, we get:
> > > >
> > > > WARNING: unmet direct dependencies detected for STACKTRACE
> > > > Depends on [n]: STACKTRACE_SUPPORT
> > > > Selected by [y]:
> > > > - STACKDEPOT [=y]
> > > >
> > > > and build errors such as:
> > > >
> > > > m68k-linux-ld: kernel/stacktrace.o: in function `stack_trace_save':
> > > > (.text+0x11c): undefined reference to `save_stack_trace'
> > > >
> > > > Add the missing deendency on STACKTRACE_SUPPORT.
> > > >
> > > > Fixes: 12a280c72868 ("drm/dp_mst: Add topology ref history tracking
> > > > for
> > > > debugging")
> > > > Cc: Lyude Paul <lyude@redhat.com>
> > > > Cc: Sean Paul <sean@poorly.run>
> > > > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> > >
> > > Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > >
> > > Gr{oetje,eeting}s,
> > >
> > > Geert
> > >
> > --
> > Cheers,
> > Lyude Paul
> >
--
Cheers,
Lyude Paul
prev parent reply other threads:[~2019-12-03 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 13:36 Guenter Roeck
2019-12-02 15:20 ` Geert Uytterhoeven
2019-12-02 18:49 ` Lyude Paul
2019-12-03 9:33 ` Daniel Vetter
2019-12-03 21:30 ` Lyude Paul [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=b35216fce6ed8f822d9147b2fa96a7cd840d96a9.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sean@poorly.run \
/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®