From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: James Hogan <james.hogan@imgtec•com>,
Joe Perches <joe@perches•com>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
linux-metag@vger•kernel.org
Subject: Re: [RFC PATCH -next] Fix printk_once build errors due to __read_mostly
Date: Thu, 31 Oct 2013 10:18:53 +1100 [thread overview]
Message-ID: <20131031101853.9fb4e06d591d0ed6be768c4e@canb.auug.org.au> (raw)
In-Reply-To: <20131030134839.8bdf70cc68d1bf0beb1fb63a@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
Hi Andrew,
On Wed, 30 Oct 2013 13:48:39 -0700 Andrew Morton <akpm@linux-foundation•org> wrote:
>
> I can't immediately think of a nice solution so I guess for now I'll
> drop printk-mark-printk_once-test-variable-__read_mostly.patch.
I have removed that from my copy of the mmotm tree.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-30 23:19 UTC|newest]
Thread overview: 13+ 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 13:46 ` Joe Perches
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 ` Stephen Rothwell [this message]
2013-10-31 18:29 ` [PATCH V3] " 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
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=20131031101853.9fb4e06d591d0ed6be768c4e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=james.hogan@imgtec$(echo .)com \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-metag@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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