mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@fluxnic.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"horms@verge.net.au" <horms@verge.net.au>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rjw@sisk.pl" <rjw@sisk.pl>,
	"lethal@linux-sh.org" <lethal@linux-sh.org>,
	"olof@lixom.net" <olof@lixom.net>
Subject: Re: [PATCH] mach-shmobile: Emma Mobile EV2 SMP prototype code
Date: Wed, 09 May 2012 09:59:56 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1205090955520.21030@xanadu.home> (raw)
In-Reply-To: <201205091345.34404.arnd@arndb.de>

On Wed, 9 May 2012, Arnd Bergmann wrote:

> FWIW, I would actually prefer merging the 'struct arm_soc_desc', 'struct
> arm_soc_smp_init_ops' and 'struct arm_soc_smp_ops' structures into a
> single 'struct smp_ops' for simplicity.

You can't easily validate correct usage of __init marked code from the 
rest if everything is pulled in the same struct.  This is why I asked 
they be split.


Nicolas

  reply	other threads:[~2012-05-09 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09  7:54 Magnus Damm
2012-05-09 12:12 ` Arnd Bergmann
2012-05-09 13:15   ` Marc Zyngier
2012-05-09 13:45     ` Arnd Bergmann
2012-05-09 13:59       ` Nicolas Pitre [this message]
2012-05-09 14:13         ` Arnd Bergmann
2012-05-09 14:52       ` Magnus Damm
2012-05-11  7:13 ` Simon Horman
2012-05-11  8:05   ` Simon Horman

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=alpine.LFD.2.02.1205090955520.21030@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=arnd@arndb.de \
    --cc=horms@verge.net.au \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=marc.zyngier@arm.com \
    --cc=olof@lixom.net \
    --cc=rjw@sisk.pl \
    /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®