Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] juno: add support for Juno r2 and point to v4.6 mainline
Date: Thu,  9 Jun 2016 11:40:29 +0100	[thread overview]
Message-ID: <cover.1465468621.git.jpinto@synopsys.com> (raw)

Add support for Juno r2 and change the kernel version to v4.6 mainline.

Joao Pinto (2):
  juno: Adding support for Juno r2
  configs/arm_juno: Point to 4.6 mainline kernel

 board/arm/juno/readme.txt  | 17 ++++++++++++++++-
 configs/arm_juno_defconfig |  9 ++++-----
 2 files changed, 20 insertions(+), 6 deletions(-)

-- 
1.8.1.5

             reply	other threads:[~2016-06-09 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 10:40 Joao Pinto [this message]
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
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=cover.1465468621.git.jpinto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox