From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jonathan Fraser <jfraser@broadcom.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"julien.grall@linaro.org" <julien.grall@linaro.org>,
"tim@xen.org" <tim@xen.org>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support
Date: Fri, 3 Oct 2014 16:29:28 +0100 [thread overview]
Message-ID: <1412350168.12695.32.camel@citrix.com> (raw)
In-Reply-To: <3D592480DD42CA41814EC9221D46F45931DDA263@SJEXCHMB12.corp.ad.broadcom.com>
On Fri, 2014-10-03 at 15:03 +0000, Jonathan Fraser wrote:
> On Fri, 2014-10-03 at 11:29 +0100, Ian Campbell wrote:
> > On Thu, 2014-10-02 at 18:16 -0400, Jon Fraser wrote:
> > > Version 2
> > >
> > > This patch series adds support for the Broadcom A15 boards based on the
> > > 7445D0 SoC. These changes only affect this single platform.
> > >
> > > The existing code for .init.proc.info and early UART support have been updated
> > > from chip version C0 to D0. Versions before D0 are not supported.
> > >
> > > I believe I've addressed all of Julien's comments on brcm.c in the previous
> > > version.
> > >
> > > Jon Fraser (4):
> > > xen/arm: Broadcom 7445D0 ARM cpu support.
> > > xen/arm: Update early print console UART address for Broadcom 7445D0.
> > > xen/arm: Add support for Broadcom 7445D0 A15 platform.
> > > xen/arm/docs: Document Broadcom 7445D0 early printk support
> >
> > All acked + applied.
> >
> > When reposting please could you collect any acked-/reviewed-by which
> > were given from the previous round (assuming you haven't made major
> > changes) into the commit log.
> >
> > Also FWIW we would normally update the docs in the same patch as
> > updating the feature.
> >
>
> I was unsure of the protocol for previously reviewed patches in a
> series. I didn't merge the doc patch with the previous in case it had
> already been applied.
http://wiki.xen.org/wiki/Submitting_Xen_Patches has some info on this,
including how to tell if something has been merged by looking at the
staging branch. The section header doesn't necessarily suggest it will
tell you this though -- I'll try and make it more obvious...
Ian.
>
>
> Thanks
> Jon
>
> > >
> > > docs/misc/arm/early-printk.txt | 1 +
> > > xen/arch/arm/Rules.mk | 2 +-
> > > xen/arch/arm/arm32/proc-v7.S | 4 +-
> > > xen/arch/arm/platforms/Makefile | 1 +
> > > xen/arch/arm/platforms/brcm.c | 294 ++++++++++++++++++++++++++++++++++++++++
> > > 5 files changed, 299 insertions(+), 3 deletions(-)
> > > create mode 100644 xen/arch/arm/platforms/brcm.c
> > >
> >
> >
> >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-03 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 22:57 [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support Jon Fraser
2014-10-01 15:28 ` Julien Grall
2014-10-02 22:16 ` [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support Jon Fraser
2014-10-02 22:16 ` [PATCH V2 1/4] xen/arm: Broadcom 7445D0 ARM cpu support Jon Fraser
2014-10-03 10:39 ` Julien Grall
2014-10-02 22:16 ` [PATCH V2 2/4] xen/arm: Update early print console UART address for Broadcom 7445D0 Jon Fraser
2014-10-02 22:16 ` [PATCH V2 3/4] xen/arm: Add support for Broadcom 7445D0 A15 platform Jon Fraser
2014-10-03 10:44 ` Julien Grall
2014-10-03 15:15 ` Jonathan Fraser
2014-10-03 15:22 ` Ian Campbell
2014-10-03 15:45 ` Jonathan Fraser
2014-10-02 22:16 ` [PATCH V2 4/4] xen/arm/docs: Document Broadcom 7445D0 early printk support Jon Fraser
2014-10-03 10:41 ` Julien Grall
2014-10-03 10:29 ` [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support Ian Campbell
2014-10-03 10:42 ` Julien Grall
2014-10-03 15:03 ` Jonathan Fraser
2014-10-03 15:29 ` Ian Campbell [this message]
2014-10-02 12:57 ` [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support Ian Campbell
2014-10-02 15:09 ` Konrad Rzeszutek Wilk
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=1412350168.12695.32.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=jfraser@broadcom.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).