From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Will Deacon <will.deacon@arm.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH v10 0/2] (arm-soc for v3.10) arm: introduce psci_smp_ops
Date: Thu, 2 May 2013 19:23:11 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1305021920070.5398@kaball.uk.xensource.com> (raw)
In-Reply-To: <20130502181851.GB14496@n2100.arm.linux.org.uk>
On Thu, 2 May 2013, Russell King - ARM Linux wrote:
> On Thu, May 02, 2013 at 06:20:32PM +0100, Stefano Stabellini wrote:
> > On Thu, 2 May 2013, Will Deacon wrote:
> > > Hi Stefano,
> > >
> > > On Thu, May 02, 2013 at 06:12:12PM +0100, Stefano Stabellini wrote:
> > > > ping
> > >
> > > Is this a ping to have this pulled into Russell's tree?
> >
> > I thought that we agreed that the patches should go via the arm-soc
> > tree, after Russell acks them.
> >
> > The ping is for Russell to ack them and Arnd to merge them.
>
> Sorry but I tend not to be around on Tuesdays and Wednesdays, which leads
> to a hell of an email problem on Thursdays. I haven't looked at them in
> any great detail (I just paged through them so far and on to the next
> email.)
No problems, if there is one person that can understand being flooded by
emails, that's me.
> I don't really have sufficient time to properly deal with all the email
> traffic that is now on this list - even from just flicking through the
> messages. It's far too much.
This patches have been discussed in great details, would you be content
with Will Deacon and Nicolas Pitre's Acks?
Nobody objected again them so far.
next prev parent reply other threads:[~2013-05-02 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 16:17 [PATCH v10 0/2] (arm-soc for v3.10) arm: introduce psci_smp_ops Stefano Stabellini
2013-04-30 16:18 ` [PATCH v10 1/2] " Stefano Stabellini
2013-04-30 16:18 ` [PATCH v10 2/2] ARM: Enable selection of SMP operations at boot time Stefano Stabellini
2013-05-02 17:12 ` [PATCH v10 0/2] (arm-soc for v3.10) arm: introduce psci_smp_ops Stefano Stabellini
2013-05-02 17:15 ` Will Deacon
2013-05-02 17:20 ` Stefano Stabellini
2013-05-02 18:18 ` Russell King - ARM Linux
2013-05-02 18:23 ` Stefano Stabellini [this message]
2013-05-02 18:28 ` Russell King - ARM Linux
2013-05-02 18:42 ` Stefano Stabellini
2013-05-02 18:48 ` Russell King - ARM Linux
2013-05-02 19:03 ` Arnd Bergmann
2013-05-02 20:34 ` Olof Johansson
2013-05-03 1:51 ` Rob Herring
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.DEB.2.02.1305021920070.5398@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).