linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] dts/ls2080a: Update DTSI to add support of SP805 WDT
Date: Fri, 25 Dec 2015 09:56:17 +0800	[thread overview]
Message-ID: <20151225015616.GA27329@dragon> (raw)
In-Reply-To: <BN3PR0301MB1298AF2C5A88FCA392D0E9DD82E70@BN3PR0301MB1298.namprd03.prod.outlook.com>

On Thu, Dec 24, 2015 at 08:41:54PM +0000, Sharma Bhupesh wrote:
> 
> 
> > -----Original Message-----
> > From: Arnd Bergmann [mailto:arnd at arndb.de]
> > Sent: Thursday, December 24, 2015 3:49 PM
> > To: Bhupesh SHARMA
> > Cc: Sharma Bhupesh-B45370; Mark Rutland; linux-arm-
> > kernel at lists.infradead.org; Olof Johansson; devicetree at vger.kernel.org;
> > Rob Herring; Will Deacon; Catalin Marinas; Li Yang-Leo-R58472; Wood
> > Scott-B07421; Yoder Stuart-B08248; shawn.guo at linaro.org
> > Subject: Re: [PATCH v3 2/2] dts/ls2080a: Update DTSI to add support of
> > SP805 WDT
> > 
> > On Wednesday 23 December 2015, Bhupesh SHARMA wrote:
> > >
> > > Hi Arnd, Olof, Kevin
> > >
> > > On Tue, Dec 15, 2015 at 8:00 PM, Bhupesh Sharma
> > > <bhupesh.sharma@freescale.com> wrote:
> > > > This patch updates the LS2080a DTSI (DTS Include) file to add
> > > > support for eight SP805 Watchdog units which can be used to reset
> > > > the eight Cortex-A57 cores available on LS2080A.
> > > >
> > > > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@freescale.com>
> > > > ---
> > > >  arch/arm64/boot/dts/freescale/fsl-ls2080a.dtsi |   56
> > ++++++++++++++++++++++++
> > > >  1 file changed, 56 insertions(+)
> > >
> > > Since Rob has acked the SP805 WDT binding documentation patch (patch
> > > 1/2 of this series),
> > > can this DTSI change, please be considered for absorption in the arm-
> > soc tree.
> > 
> > Sure, please submit it for inclusion. Who is the maintainer for
> > arch/arm64/boot/dts/freescale/ ? Can they pick up all the freescale
> > related dts changes and submit them as a pull request? Should they go
> > through Shawn's tree maybe?
> 
> Thanks Arnd. For now, may-be I can send this patchset with Rob's Acked-by added
> for 1/2 to 'arm at kernel.org'. So that this can be picked by via the arm-soc tree.
> Shawn, I hope it's ok with you.

Yeah.  I'm maintaining a git tree, collecting all Freescale arm32
platform patches, and sending them to arm-soc for each merge window.
If I can be copied on those arm64 patches, I do not mind handling them
together with arm32 ones.

Shawn

  reply	other threads:[~2015-12-25  1:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 14:30 [PATCH v3 0/2] ARM64: Enable SP805 WDT support for FSL LS2080A Bhupesh Sharma
2015-12-15 14:30 ` [PATCH v3 1/2] Documentation: DT: Add entry for ARM SP805-WDT Bhupesh Sharma
2015-12-20  3:38   ` Rob Herring
2015-12-15 14:30 ` [PATCH v3 2/2] dts/ls2080a: Update DTSI to add support of SP805 WDT Bhupesh Sharma
2015-12-23  5:23   ` Bhupesh SHARMA
2015-12-24 10:18     ` Arnd Bergmann
2015-12-24 20:41       ` Sharma Bhupesh
2015-12-25  1:56         ` Shawn Guo [this message]
2015-12-28  9:48           ` Bhupesh SHARMA
2016-01-12 14:17           ` Li Yang
2015-12-18  6:22 ` [PATCH v3 0/2] ARM64: Enable SP805 WDT support for FSL LS2080A Bhupesh SHARMA

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=20151225015616.GA27329@dragon \
    --to=shawnguo@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).