From: Joe Perches <joe@perches.com>
To: James Hogan <james.hogan@imgtec.com>,
Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH -next] Fix printk_once build errors due to __read_mostly
Date: Wed, 30 Oct 2013 09:07:45 -0700 [thread overview]
Message-ID: <1383149265.9435.19.camel@joe-AO722> (raw)
In-Reply-To: <1383128301-20231-1-git-send-email-james.hogan@imgtec.com>
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?
Is there a list somewhere of what arches are build tested?
cheers, Joe
next prev parent reply other threads:[~2013-10-30 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 10:18 James Hogan
2013-10-30 13:46 ` Joe Perches
2013-10-30 16:07 ` Joe Perches [this message]
2013-10-31 14:54 ` Fengguang Wu
2013-10-30 17:02 ` Joe Perches
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-30 23:18 ` [RFC PATCH -next] Fix printk_once build errors due to __read_mostly 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
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=1383149265.9435.19.camel@joe-AO722 \
--to=joe@perches.com \
--cc=fengguang.wu@intel.com \
--cc=james.hogan@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®