From: Thierry Reding <thierry.reding@gmail.com>
To: 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>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build failure after merge of the drm-tegra tree
Date: Mon, 4 Feb 2019 08:30:03 +0100 [thread overview]
Message-ID: <20190204073003.GB16448@ulmo> (raw)
In-Reply-To: <20190204111241.278b6215@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Mon, Feb 04, 2019 at 11:12:41AM +1100, Stephen Rothwell wrote:
> Hi Thierry,
>
> After merging the drm-tegra tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpu/host1x/cdma.c: In function 'host1x_cdma_wait_pushbuffer_space':
> drivers/gpu/host1x/cdma.c:279:13: error: 'struct host1x_cdma' has no member named 'sem'
> down(&cdma->sem);
> ^~
>
> Caused by commit
>
> abb289796799 ("gpu: host1x: Use completion instead of semaphore")
>
> interacting with commit
>
> db5652be58a9 ("gpu: host1x: Introduce support for wide opcodes")
>
> I have used the drm-tegra tree from next-20190201 for today.
Oh my... so I go through all the build testing and then pull in the
seemlessly harmless fix and ruin everything...
I've fixed it up in my tree now, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-04 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 0:12 linux-next: build failure after merge of the drm-tegra tree Stephen Rothwell
2019-02-04 7:30 ` Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 8:08 Stephen Rothwell
2014-08-04 4:18 Stephen Rothwell
2014-02-27 1:53 Stephen Rothwell
2014-02-27 12:10 ` Thierry Reding
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=20190204073003.GB16448@ulmo \
--to=thierry.reding@gmail.com \
--cc=arnd@arndb.de \
--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).