All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Joe Perches <joe@perches.com>
Cc: James Hogan <james.hogan@imgtec.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH -next] Fix printk_once build errors due to __read_mostly
Date: Thu, 31 Oct 2013 22:54:52 +0800	[thread overview]
Message-ID: <20131031145452.GB2277@localhost> (raw)
In-Reply-To: <1383149265.9435.19.camel@joe-AO722>

Hi Joe,

On Wed, Oct 30, 2013 at 09:07:45AM -0700, Joe Perches wrote:
> On Wed, 2013-10-30 at 10:18 +0000, James Hogan wrote:
> > Commit 3e39c1ab04ba (printk: mark printk_once test variable
> > __read_mostly) added __read_mostly to the __print_once bool in the
> > printk_once() macro, but __read_mostly is defined in <linux/cache.h>
> > which isn't included from <linux/printk.h>. This results in build errors
> > like this:
> > 
> > arch/metag/mm/l2cache.c: In function 'meta_l2c_setup':
> > arch/metag/mm/l2cache.c:56: error: '__read_mostly' undeclared
> 
> Fengguang?
> 
> Do you have the metag arch cross-compiler in your auto build tests?

Nope.

> Is there a list somewhere of what arches are build tested?

It's pretty much all the ones supported by

        https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/

Here are my installed ones (the highest version will be used if there
are several versions available):

gcc-4.2.4-nolibc/avr32-linux     gcc-4.6.3-nolibc/frv-linux     gcc-4.6.3-nolibc/mips64-linux     gcc-4.6.3-nolibc/sparc-linux
gcc-4.5.1-nolibc/or32-linux      gcc-4.6.3-nolibc/hppa64-linux  gcc-4.6.3-nolibc/mips-linux       gcc-4.6.3-nolibc/x86_64-linux
gcc-4.6.2-nolibc/tilegx-linux    gcc-4.6.3-nolibc/hppa-linux    gcc-4.6.3-nolibc/powerpc64-linux  gcc-4.6.3-nolibc/xtensa-linux
gcc-4.6.3-nolibc/alpha-linux     gcc-4.6.3-nolibc/i386-linux    gcc-4.6.3-nolibc/powerpc-linux    gcc-4.8.0-nolibc/microblaze-linux
gcc-4.6.3-nolibc/am33_2.0-linux  gcc-4.6.3-nolibc/ia64-linux    gcc-4.6.3-nolibc/s390x-linux      gcc-4.8.0-nolibc/powerpc64-linux
gcc-4.6.3-nolibc/cris-linux      gcc-4.6.3-nolibc/m32r-linux    gcc-4.6.3-nolibc/sh4-linux
gcc-4.6.3-nolibc/crisv32-linux   gcc-4.6.3-nolibc/m68k-linux    gcc-4.6.3-nolibc/sparc64-linux

Thanks,
Fengguang

  reply	other threads:[~2013-10-31 14:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 10:18 [RFC PATCH -next] Fix printk_once build errors due to __read_mostly James Hogan
2013-10-30 10:18 ` James Hogan
2013-10-30 13:46 ` Joe Perches
2013-10-30 16:07 ` Joe Perches
2013-10-31 14:54   ` Fengguang Wu [this message]
2013-10-30 17:02 ` Joe Perches
2013-10-30 20:48 ` Andrew Morton
2013-10-30 20:48   ` Andrew Morton
2013-10-30 22:58   ` Joe Perches
2013-10-30 23:01   ` [PATCH V2] printk/cache: Mark printk_once test variable __read_mostly Joe Perches
2013-10-31 13:35     ` James Hogan
2013-10-31 13:35       ` James Hogan
2013-10-30 23:18   ` [RFC PATCH -next] Fix printk_once build errors due to __read_mostly Stephen Rothwell
2013-10-30 23:18     ` Stephen Rothwell
2013-10-31 18:29   ` [PATCH V3] printk/cache: Mark printk_once test variable __read_mostly Joe Perches
2013-11-13  0:23     ` Tony Luck
2013-11-13  0:29       ` Joe Perches
2013-11-13 19:31         ` Tony Luck
     [not found]           ` <CA+8MBbJKN174=ybMNE7Z+oT7KjNBzgdy9cvhb_kACvXAbTo9XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-14  1:16             ` Joe Perches
2013-11-14  1:16               ` Joe Perches

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=20131031145452.GB2277@localhost \
    --to=fengguang.wu@intel.com \
    --cc=james.hogan@imgtec.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@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.