From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: shmobile: r8a7791: Correct number of CPU cores
Date: Wed, 05 Nov 2014 01:56:38 +0000 [thread overview]
Message-ID: <20141105015637.GA32470@verge.net.au> (raw)
In-Reply-To: <CANqRtoT4FezTLYr0RC9QzwwHSTSbMA4aJC70K3J42_O22BAgXw@mail.gmail.com>
On Wed, Nov 05, 2014 at 10:23:34AM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Wed, Nov 5, 2014 at 9:36 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Fri, Oct 24, 2014 at 05:33:07PM +0900, Simon Horman wrote:
> >> Hi,
> >>
> >> this short series separates AMPU resource data as it is not
> >> common accross R-Car gen2 SoCs: only the r8a7790 (H1) has the resouces
> >> described. It then corrects the resource data for the r8a7791,
> >> the only other SoC currently present in mainline that uses this data.
> >>
> >> Based on the renesas-next-20141024-v3.18-rc1 tag of my renesas tree.
> >>
> >> Hisashi Nakamura (2):
> >> ARM: shmobile: Separate APMU resource data into CPU dependant part
> >> ARM: shmobile: r8a7791: Correct number of CPU cores
> >
> > I have queued up this series.
>
> Thanks. I didn't say anything so I should probably be silent, but in
> the future it would make sense to fold in the fix into the original
> patch to void merging broken stuff.
I'm not quite sure what you are getting at in relation to this series,
but yes, in general I agree.
prev parent reply other threads:[~2014-11-05 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 8:33 [PATCH 0/2] ARM: shmobile: r8a7791: Correct number of CPU cores Simon Horman
2014-10-24 8:33 ` [PATCH 1/2] ARM: shmobile: Separate APMU resource data into CPU dependant part Simon Horman
2014-10-24 8:33 ` [PATCH 2/2] ARM: shmobile: r8a7791: Correct number of CPU cores Simon Horman
2014-11-05 0:36 ` [PATCH 0/2] " Simon Horman
2014-11-05 1:23 ` Magnus Damm
2014-11-05 1:56 ` Simon Horman [this message]
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=20141105015637.GA32470@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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