public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation•org>
To: paulmck@linux•vnet.ibm.com
Cc: Richard Weinberger <richard@nod•at>,
	Randy Dunlap <rdunlap@infradead•org>,
	Rik van Riel <riel@redhat•com>,
	linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
	umgwanakikbuti@gmail•com
Subject: Re: mmotm 2014-04-24-13-07 uploaded
Date: Mon, 28 Apr 2014 16:05:01 -0700	[thread overview]
Message-ID: <20140428160501.df072b191fce77ab5d042054@linux-foundation.org> (raw)
In-Reply-To: <20140428213909.GA16623@linux.vnet.ibm.com>

On Mon, 28 Apr 2014 14:39:09 -0700 "Paul E. McKenney" <paulmck@linux•vnet.ibm.com> wrote:

> On Mon, Apr 28, 2014 at 01:06:40PM -0700, Paul E. McKenney wrote:
> > On Mon, Apr 28, 2014 at 07:21:27PM +0200, Richard Weinberger wrote:
> > > Am 28.04.2014 19:17, schrieb Randy Dunlap:
> > > > 
> > > > uml defconfig on x86_64:
> > > > 
> > > >   CC      arch/um/kernel/asm-offsets.s
> > > > In file included from include/linux/sem.h:5:0,
> > > >                  from include/linux/sched.h:35,
> > > >                  from arch/x86/um/shared/sysdep/kernel-offsets.h:2,
> > > >                  from arch/um/kernel/asm-offsets.c:1:
> > > > include/linux/rcupdate.h:257:20: error: static declaration of 'rcu_sysrq_start' follows non-static declaration
> > > > include/linux/rcupdate.h:250:6: note: previous declaration of 'rcu_sysrq_start' was here
> > > > include/linux/rcupdate.h:260:20: error: static declaration of 'rcu_sysrq_end' follows non-static declaration
> > > > include/linux/rcupdate.h:251:6: note: previous declaration of 'rcu_sysrq_end' was here
> > > > make[2]: *** [arch/um/kernel/asm-offsets.s] Error 1
> > > > 
> > > > 
> > > > Please test your patch(es).
> > 
> > Against exactly what?  ;-)
> > 
> > > Just in case, to build an x86_64 UML please run:
> > > 
> > > make defconfig ARCH=um SUBARCH=x86_64
> > > make linux ARCH=um SUBARCH=x86_64
> > 
> > Hmmm....  Builds without errors in my local tree.
> > 
> > Make a clone of linux-next...
> > 
> > OK, now I get a different build failure:
> > 

OK, my tiny brain just burst.  Rik, I think I shall ease

sysrq-rcu-ify-__handle_sysrq.patch
sysrq-rcu-ify-__handle_sysrq-fix.patch
and
sysrqrcu-suppress-rcu-stall-warnings-while-sysrq-runs.patch

into the bitbucket for now.  Please resend everything when it's all
sorted out?

  reply	other threads:[~2014-04-28 23:05 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
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 [this message]
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=20140428160501.df072b191fce77ab5d042054@linux-foundation.org \
    --to=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=paulmck@linux$(echo .)vnet.ibm.com \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=richard@nod$(echo .)at \
    --cc=riel@redhat$(echo .)com \
    --cc=umgwanakikbuti@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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