From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org
Subject: Re: build failure after merge of the rcu tree
Date: Mon, 9 Oct 2017 12:43:41 -0700 [thread overview]
Message-ID: <20171009194341.GK3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171009170540.45xwjhyvdwiwxcxe@sirena.co.uk>
On Mon, Oct 09, 2017 at 06:05:40PM +0100, Mark Brown wrote:
> After merging the rcu tree an arm64 defconfig fails to build with:
>
> /home/broonie/tmpfs/next/drivers/firmware/tegra/ivc.c: In function 'tegra_ivc_ad
> vance_tx':
> /home/broonie/tmpfs/next/drivers/firmware/tegra/ivc.c:154:39: error: lvalue required as left operand of assignment
> READ_ONCE(ivc->tx.channel->tx.count) =
> ^
> /home/broonie/tmpfs/next/drivers/firmware/tegra/ivc.c: In function 'tegra_ivc_advance_rx':
> /home/broonie/tmpfs/next/drivers/firmware/tegra/ivc.c:165:39: error: lvalue required as left operand of assignment
> READ_ONCE(ivc->rx.channel->rx.count) =
> ^
> /home/broonie/tmpfs/next/scripts/Makefile.build:313: recipe for target 'drivers/firmware/tegra/ivc.o' failed
>
> caused by 669f98e232aa6f77bd60 ("drivers/firmware/tegra: Convert
> ACCESS_ONCE() to READ_ONCE()") in the rcu tree. I've reverted to the
> RCU version from September 28th (which is already in Linus' tree).
And this one is me having failed to push that last fix out. But the
whole commit is going away in favor of Mark Rutland's Coccinelle script
anyway.
Thanx, Paul
prev parent reply other threads:[~2017-10-09 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:05 build failure after merge of the rcu tree Mark Brown
2017-10-09 17:17 ` Mark Brown
2017-10-09 19:42 ` Paul E. McKenney
2017-10-09 19:43 ` Paul E. McKenney [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=20171009194341.GK3521@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=broonie@kernel.org \
--cc=linux-next@vger.kernel.org \
/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).