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:42:35 -0700 [thread overview]
Message-ID: <20171009194235.GJ3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171009171724.frgul6w6ggbirgns@sirena.co.uk>
On Mon, Oct 09, 2017 at 06:17:24PM +0100, Mark Brown wrote:
> On Mon, Oct 09, 2017 at 06:05:40PM +0100, Mark Brown wrote:
>
> > 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).
>
> BTW there were also a bunch of merge issues that I sent out mails for
> but they seem to have gone AWOL somewhere, don't know if you got them :/
Hello, Mark,
I did get three of them, thank you! The one involving rcu_irq_enter()
is because one of my commits hit mainline early, so I will need to rebase
to get things straightened out. Almost all of the ACCESS_ONCE() commits
are going away, courtesy of Mark Rutland's Coccinelle script. The one
involving the timer will be resolved by my updating my diagnostic commit.
All in all, I should have left some of these commits out of rcu/next,
apologies for the noise!
Thanx, Paul
next prev parent reply other threads:[~2017-10-09 19:42 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 [this message]
2017-10-09 19:43 ` Paul E. McKenney
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=20171009194235.GJ3521@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.