From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rusty Russell <rusty@rustcorp•com.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Randy Dunlap <randy.dunlap@oracle•com>
Subject: Re: linux-next: Tree for January 8 (percpu)
Date: Fri, 9 Jan 2009 09:23:22 +1100 [thread overview]
Message-ID: <20090109092322.fd43b3b6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <496636AB.9000903@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
(Forward to Rusty)
On Thu, 08 Jan 2009 09:23:55 -0800 Randy Dunlap <randy.dunlap@oracle•com> wrote:
>
> Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20090107:
> >
> > Undropped tree:
> > rr
> >
> > Dropped trees (temporarily):
> > ocfs2 (build problem)
> > cpu_alloc (build problem)
>
>
> When CONFIG_SMP=n, both arch/x86/include/asm/percpu.h and
> include/asm-generic/percpu.h define both of
> read_percpu_ptr() and read_percpu_var().
>
>
> build-r8079.out:linux-next-20090108/include/asm-generic/percpu.h:124:1: warning: "read_percpu_ptr" redefined
> build-r8079.out:linux-next-20090108/arch/x86/include/asm/percpu.h:107:1: warning: this is the location of the previous definition
> build-r8079.out:linux-next-20090108/include/asm-generic/percpu.h:120:1: warning: "read_percpu_var" redefined
> build-r8079.out:linux-next-20090108/arch/x86/include/asm/percpu.h:106:1: warning: this is the location of the previous definition
>
>
>
> --
> ~Randy
>
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-08 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 6:17 linux-next: Tree for January 8 Stephen Rothwell
2009-01-08 17:23 ` linux-next: Tree for January 8 (percpu) Randy Dunlap
2009-01-08 22:23 ` Stephen Rothwell [this message]
2009-01-10 6:18 ` Rusty Russell
2009-01-08 17:44 ` linux-next: Tree for January 8 (multimedia/cx88) Randy Dunlap
2009-01-08 20:14 ` Mauro Carvalho Chehab
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=20090109092322.fd43b3b6.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=rusty@rustcorp$(echo .)com.au \
/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