All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] juno: Adding support for Juno r2
Date: Mon, 13 Jun 2016 16:55:07 +0000	[thread overview]
Message-ID: <6C7E76B729B341419CE4B84926C1D2CD011D32CD@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <20160609220352.5586fe0b@free-electrons.com>

Thanks Thomas.

-----Original Message-----
From: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com] 
Sent: Thursday, June 09, 2016 9:04 PM
To: Joao Pinto <Joao.Pinto@synopsys.com>
Cc: buildroot at buildroot.org; Liviu.Dudau at arm.com; CARLOS.PALMINHA at synopsys.com
Subject: Re: [Buildroot] [PATCH 1/2] juno: Adding support for Juno r2

Hello,

The title should have been:

	configs/arm_juno: add support for Juno r2

On Thu,  9 Jun 2016 11:40:30 +0100, Joao Pinto wrote:
> Add support for Juno r2.

This part is not needed, as it only repeats the commit title with no other additional information.

>  Preparing your rootfs
> @@ -89,6 +91,19 @@ NOR3LOAD: 00000000               ;Image Load Address
>  NOR3ENTRY: 00000000              ;Image Entry Point
>  ......
>  
> +Configure *.dtb in the boot configuration for Juno r1

I guess you meant r2 here.

Applied with those issues fixed.

Thanks!

Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering http://free-electrons.com

  reply	other threads:[~2016-06-13 16:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 10:40 [Buildroot] [PATCH 0/2] juno: add support for Juno r2 and point to v4.6 mainline Joao Pinto
2016-06-09 10:40 ` [Buildroot] [PATCH 1/2] juno: Adding support for Juno r2 Joao Pinto
2016-06-09 20:03   ` Thomas Petazzoni
2016-06-13 16:55     ` Joao Pinto [this message]
2016-06-09 10:40 ` [Buildroot] [PATCH 2/2] configs/arm_juno: Point to 4.6 mainline kernel Joao Pinto
2016-06-09 20:07   ` Thomas Petazzoni

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=6C7E76B729B341419CE4B84926C1D2CD011D32CD@de02wembxa.internal.synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.