From: Dave Airlie <airlied@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: build warning after merge of the drm tree
Date: Mon, 4 Dec 2017 10:57:40 +1000 [thread overview]
Message-ID: <CAPM=9tx6Q3KdMhUwK=RS0vOVqZRN_EQ4V0i6pKi8b5vOh6ZBhA@mail.gmail.com> (raw)
In-Reply-To: <20171204113021.074df7b8@canb.auug.org.au>
On 4 December 2017 at 10:30, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
Oops, not sure how I missed it, force pushed drm-next with the merge fixed.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-12-04 0:57 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 0:30 linux-next: build warning after merge of the drm tree Stephen Rothwell
2017-12-04 0:57 ` Dave Airlie [this message]
2018-02-18 23:18 Stephen Rothwell
2018-03-02 1:49 ` Stephen Rothwell
2018-06-25 4:22 Stephen Rothwell
2018-06-25 4:22 ` Stephen Rothwell
2019-02-01 0:53 Stephen Rothwell
2020-05-11 3:47 Stephen Rothwell
2020-05-11 4:04 ` Randy Dunlap
2020-09-23 3:36 Stephen Rothwell
2020-09-23 6:27 ` Tomi Valkeinen
2020-10-01 9:47 ` Stephen Rothwell
2020-11-05 7:02 Stephen Rothwell
2020-11-16 0:01 ` Stephen Rothwell
2021-01-22 0:59 Stephen Rothwell
2021-01-22 7:17 ` Daniel Vetter
2021-01-22 7:29 ` Stephen Rothwell
2021-01-22 8:40 ` Daniel Vetter
2021-10-27 12:12 ` Joonas Lahtinen
2021-10-27 20:51 ` Stephen Rothwell
2021-10-28 9:16 ` Joonas Lahtinen
2021-02-01 1:55 ` Stephen Rothwell
2021-03-17 2:53 Stephen Rothwell
2021-03-17 7:42 Stephen Rothwell
2021-04-01 7:19 Stephen Rothwell
2021-04-21 6:28 ` Stephen Rothwell
2022-02-02 4:02 Stephen Rothwell
2022-02-02 4:03 ` Stephen Rothwell
2022-02-02 8:38 ` Hans de Goede
2022-02-04 19:29 ` Rajat Jain
2022-03-02 1:34 ` Stephen Rothwell
2022-03-02 10:32 ` Hans de Goede
2022-03-02 11:38 ` Stephen Rothwell
2022-02-02 4:10 Stephen Rothwell
2022-03-02 1:32 ` Stephen Rothwell
2022-11-07 3:29 Stephen Rothwell
2022-11-07 20:31 ` John Harrison
2023-01-05 3:17 Stephen Rothwell
2023-01-05 3:21 Stephen Rothwell
2023-01-05 3:43 Stephen Rothwell
2023-02-03 2:46 Stephen Rothwell
2023-02-03 12:32 ` Gustavo Sousa
2023-03-30 3:28 Stephen Rothwell
2023-03-30 14:28 ` Rob Clark
2023-07-11 23:17 ` Stephen Rothwell
2023-07-24 3:50 ` Stephen Rothwell
2023-04-11 6:01 Stephen Rothwell
2023-04-11 6:02 Stephen Rothwell
2023-04-11 9:48 ` Andi Shyti
2023-11-24 2:17 Stephen Rothwell
2023-11-24 2:23 Stephen Rothwell
2023-11-24 2:25 Stephen Rothwell
2023-11-24 12:35 ` Donald Robson
2024-01-02 0:12 Stephen Rothwell
2024-01-03 1:19 ` Stephen Rothwell
2024-01-03 1:27 ` Stephen Rothwell
2024-01-04 16:52 ` Jani Nikula
2024-01-05 6:47 Stephen Rothwell
2024-01-25 0:33 ` Stephen Rothwell
2024-01-26 8:48 ` Thomas Hellström
2024-02-07 6:17 Stephen Rothwell
2024-02-07 14:19 ` Rodrigo Vivi
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='CAPM=9tx6Q3KdMhUwK=RS0vOVqZRN_EQ4V0i6pKi8b5vOh6ZBhA@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).