From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM and OMAP patches to avoid lockdep complaints
Date: Thu, 16 Jun 2016 21:07:09 -0700 [thread overview]
Message-ID: <20160617040708.GA22406@atomide.com> (raw)
In-Reply-To: <20160615210926.GA30957@linux.vnet.ibm.com>
Hi,
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> [160615 14:11]:
> Hello!
>
> Ingo was not comfortable taking these through -tip, which is understandable,
> given that they don't depend on each other or on anything else not already
> in mainline, and that they don't have anything to do with -tip.
>
> So what would you guys like to do with these?
I'll merge it into omap-for-v4.7/fixes thanks.
Regards,
Tony
> They may be pulled from 7c64cc0531fa (arm: Use _rcuidle for
> smp_cross_call() tracepoints) in my -rcu tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
>
> Thanx, Paul
>
next prev parent reply other threads:[~2016-06-17 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 21:09 ARM and OMAP patches to avoid lockdep complaints Paul E. McKenney
2016-06-17 4:07 ` Tony Lindgren [this message]
2016-06-17 12:58 ` 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=20160617040708.GA22406@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).