From: Joonas Lahtinen <joonas.lahtinen@linux•intel.com>
To: DRI <dri-devel@lists•freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll•ch>,
Intel Graphics <intel-gfx@lists•freedesktop.org>,
Jani Nikula <jani.nikula@linux•intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel•com>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Matthew Auld <matthew.auld@intel•com>
Subject: Re: linux-next: build failure after merge of the drm-intel-fixes tree
Date: Tue, 21 Jan 2020 09:13:24 +0200 [thread overview]
Message-ID: <157959080456.6877.8085345204229334781@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200121083424.66d98dc5@canb.auug.org.au>
Quoting Stephen Rothwell (2020-01-20 23:34:24)
> Hi all,
>
> After merging the drm-intel-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
>
> Caused by commit
>
> d8fcca47e195 ("drm/i915/userptr: fix size calculation")
>
> I have reverted that commit for today.
It was a missing git add while fixing a cherry-pick and is now fixed.
Regards, Joonas
next prev parent reply other threads:[~2020-01-21 7:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 21:34 linux-next: build failure after merge of the drm-intel-fixes tree Stephen Rothwell
2020-01-21 7:13 ` Joonas Lahtinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-13 12:14 Stephen Rothwell
2022-01-31 22:27 Stephen Rothwell
2020-11-03 22:37 Stephen Rothwell
2020-11-04 0:25 ` Rodrigo Vivi
2020-06-15 23:39 Stephen Rothwell
2020-06-16 9:22 ` Joonas Lahtinen
2020-05-28 22:30 Stephen Rothwell
2019-01-29 22:39 Stephen Rothwell
2019-01-29 22:53 ` Lucas De Marchi
2019-01-30 8:22 ` Jani Nikula
2018-05-29 9:26 Stephen Rothwell
2018-05-29 11:45 ` Joonas Lahtinen
2017-10-10 7:03 Mark Brown
2017-10-11 8:51 ` Mark Brown
2017-01-02 23:42 Stephen Rothwell
2017-01-03 2:59 ` Zhenyu Wang
2017-01-03 4:07 ` Stephen Rothwell
2017-01-03 4:48 ` Alex Williamson
2017-01-03 9:23 ` Zhenyu Wang
2017-01-03 13:25 ` Jani Nikula
2017-01-03 20:37 ` Alex Williamson
2017-01-04 9:07 ` Daniel Vetter
2014-06-06 2:03 Stephen Rothwell
2014-06-06 6:45 ` Daniel Vetter
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=157959080456.6877.8085345204229334781@jlahtine-desk.ger.corp.intel.com \
--to=joonas.lahtinen@linux$(echo .)intel.com \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=jani.nikula@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matthew.auld@intel$(echo .)com \
--cc=rodrigo.vivi@intel$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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