public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: "Hawkins, Nick" <nick.hawkins@hpe.com>
Cc: "Verdun, Jean-Marie" <verdun@hpe.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
Date: Fri, 3 Jun 2022 09:23:11 -0400	[thread overview]
Message-ID: <20220603132311.GD1958597@bill-the-cat> (raw)
In-Reply-To: <DM4PR84MB192704FF0D2184708313D39088DE9@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Thu, Jun 02, 2022 at 08:56:59PM +0000, Hawkins, Nick wrote:
> 
> 
> -----Original Message-----
> From: Hawkins, Nick 
> Sent: Thursday, June 2, 2022 3:56 PM
> To: Tom Rini <trini@konsulko.com>
> Cc: Verdun, Jean-Marie <verdun@hpe.com>; u-boot@lists.denx.de
> Subject: RE: [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc
> 
> > > > The dts files need to be in linux-next (or similar) upstream before we start taking them in to Linux, and then re-synced periodically.
> > > 
> > > Hi Tom,
> > > 
> > > When you say taking them into Linux do you mean these files for U-Boot would go into Torvalds Linux? Ideally we would like to have the one from Torvalds Linux come into U-boot. Our DTS files are currently here at Linux-next:
> > > 
> > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts
> 
> > Correct, we want to use those files as-is, and then only append to them via a "-u-boot.dtsi" file.
> 
> Hi Tom,
> 
> I accidently hit return. Will I need to manually merge these files from Linux or will someone else do that?

You will need to post a sync periodically.  Every Linux release (full,
not -rc) would be great, every couple is fine.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-06-03 13:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 18:55 [PATCH v1 1/9] ARM: hpe: gxp: add core support nick.hawkins
2022-05-26 18:55 ` [PATCH v1 2/9] timer: gxp: Add HPE GXP timer support nick.hawkins
2022-05-26 18:55 ` [PATCH v1 3/9] board: hpe: gxp: add HPE GXP soc support nick.hawkins
2022-06-01 14:24   ` Tom Rini
2022-05-26 18:55 ` [PATCH v1 4/9] dt-bindings: arm: hpe: add GXP Support nick.hawkins
2022-05-26 18:55 ` [PATCH v1 5/9] dt-bindings: timer: Add hpe gxp timer nick.hawkins
2022-05-26 18:55 ` [PATCH v1 6/9] ARM: dts: Add device tree files for hpe gxp soc nick.hawkins
2022-06-01 14:24   ` Tom Rini
2022-06-01 14:50     ` Hawkins, Nick
2022-06-01 15:28       ` Tom Rini
2022-06-02 20:56         ` Hawkins, Nick
2022-06-02 20:56           ` Hawkins, Nick
2022-06-03 13:23             ` Tom Rini [this message]
2022-06-03 15:35               ` Hawkins, Nick
2022-06-03 16:24                 ` Tom Rini
2022-05-26 18:55 ` [PATCH v1 7/9] configs: gxp: add core support nick.hawkins
2022-06-01 14:24   ` Tom Rini
2022-06-02 14:46     ` Hawkins, Nick
2022-06-02 14:50       ` Tom Rini
2022-05-26 18:55 ` [PATCH v1 8/9] configs: gxp: add gxp_defconfig nick.hawkins
2022-05-26 18:55 ` [PATCH v1 9/9] MAINTAINERS: Introduce HPE GXP Architecture nick.hawkins

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=20220603132311.GD1958597@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=nick.hawkins@hpe.com \
    --cc=u-boot@lists.denx.de \
    --cc=verdun@hpe.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