public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: dhowells@redhat.com, Jeremy Fitzhardinge <jeremy@goop.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	tj@kernel.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FRV: Fix the section attribute on UP DECLARE_PER_CPU()
Date: Wed, 15 Apr 2009 16:09:10 +0100	[thread overview]
Message-ID: <9843.1239808150@redhat.com> (raw)
In-Reply-To: <20090415140959.GD12760@elte.hu>

Ingo Molnar <mingo@elte.hu> wrote:

> > > Please create include/linux/percpu_types.h for basic data types 
> > > and simple, self-sufficient primitives. Also have an 
> > > include/linux/percpu_api.h or include/linux/percpu.h include 
> > > file for convenience/speedup inlines. The latter will only be 
> > > included in .c files, where 'combination' of type spaces is not 
> > > a problem.
> > 
> > Not so.  The problem is that various header files make use of 
> > per-cpu variable accessors (asm/current.h and asm/thread_info.h to 
> > name a couple) to build inline asm.
> 
> Hm, what portion did you mark with 'not so'?

The statement that "The latter will only be included in .c files, where
'combination' of type spaces is not a problem".

> I dont disagree, but i'd like to warn that such patches need _way_ 
> more testing, these are never same-day obvious patches.

I can't argue with that.

I'd like Linus to pull my first patch, if he will.  That'll at least allow FRV
to build.  Could you review it?  That's the email that started this thread,
ensubjected:

	[PATCH] FRV: Fix the section attribute on UP DECLARE_PER_CPU()

David

  reply	other threads:[~2009-04-15 15:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 16:10 [PATCH] FRV: Fix the section attribute on UP DECLARE_PER_CPU() David Howells
2009-04-14 16:57 ` Linus Torvalds
2009-04-14 17:57   ` David Howells
2009-04-14 18:06     ` Linus Torvalds
2009-04-15 10:24       ` David Howells
2009-04-15 15:19         ` Linus Torvalds
2009-04-15 16:49           ` Ingo Molnar
2009-04-15 11:40       ` David Howells
2009-04-15 12:03         ` Ingo Molnar
2009-04-15 13:20           ` David Howells
2009-04-15 14:09             ` Ingo Molnar
2009-04-15 15:09               ` David Howells [this message]
2009-04-15 16:54                 ` Ingo Molnar
2009-04-21 18:36                   ` David Howells
2009-04-22  9:12                     ` Ingo Molnar

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=9843.1239808150@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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