From: Rik van Riel <riel@redhat.com>
To: paulmck@linux.vnet.ibm.com, Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
linux-next@vger.kernel.org
Subject: Re: mmotm 2014-04-24-13-07 uploaded
Date: Fri, 25 Apr 2014 09:25:55 -0400 [thread overview]
Message-ID: <535A6263.10009@redhat.com> (raw)
In-Reply-To: <20140425024924.GR4496@linux.vnet.ibm.com>
On 04/24/2014 10:49 PM, Paul E. McKenney wrote:
> On Thu, Apr 24, 2014 at 03:40:29PM -0700, Randy Dunlap wrote:
>> On 04/24/14 13:08, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2014-04-24-13-07 has been uploaded to
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
>>> more than once a week.
>>>
>>> You will need quilt to apply these patches to the latest Linus release (3.x
>>> or 3.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
>>> http://ozlabs.org/~akpm/mmotm/series
>>>
>>
>> uml on x86_64 defconfig:
>>
>> drivers/built-in.o: In function `__handle_sysrq':
>> drivers/tty/sysrq.c:514: undefined reference to `rcu_sysrq_start'
>> drivers/tty/sysrq.c:558: undefined reference to `rcu_sysrq_end'
>
> Hmmm... Looks like Rik's patch needs declarations in rcupdate.h.
> Not sure how I missed that... :-/
Looks like maybe sysrq.c should explicitly #include rcupdate.h.
On x86-64 the code compiled just fine, because something else
included rcupdate.h. Apparently on UML this breaks...
--
All rights reversed
next prev parent reply other threads:[~2014-04-25 13:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:08 mmotm 2014-04-24-13-07 uploaded akpm
2014-04-24 22:40 ` Randy Dunlap
2014-04-25 2:49 ` Paul E. McKenney
2014-04-25 11:37 ` Rik van Riel
2014-04-25 13:25 ` Rik van Riel [this message]
2014-04-25 14:04 ` Rik van Riel
2014-04-25 20:44 ` Randy Dunlap
2014-04-25 20:52 ` Randy Dunlap
2014-04-27 6:26 ` Paul E. McKenney
2014-04-27 17:27 ` Randy Dunlap
2014-04-27 20:40 ` Randy Dunlap
2014-04-28 0:26 ` Paul E. McKenney
2014-04-28 13:55 ` Paul E. McKenney
2014-04-28 17:17 ` Randy Dunlap
2014-04-28 17:21 ` Richard Weinberger
2014-04-28 20:06 ` Paul E. McKenney
2014-04-28 20:32 ` Randy Dunlap
2014-04-28 21:15 ` Paul E. McKenney
2014-04-28 21:59 ` Randy Dunlap
2014-04-29 12:07 ` Rik van Riel
2014-04-29 16:36 ` Paul E. McKenney
2014-04-29 17:31 ` Rik van Riel
2014-04-29 17:45 ` Paul E. McKenney
2014-04-28 21:39 ` Paul E. McKenney
2014-04-28 23:05 ` Andrew Morton
2014-04-28 23:42 ` Stephen Rothwell
2014-04-24 22:51 ` mmotm 2014-04-24-13-07 uploaded (regulator/arizona-ldo1.c) Randy Dunlap
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=535A6263.10009@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
/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).