All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] configs/friendlyarm_nanopi_neo_plus2: use an extlinux instead of uEnv.txt
Date: Sat, 26 Oct 2019 20:07:08 +0200	[thread overview]
Message-ID: <20191026200708.35ed4e8c@windsurf.home> (raw)
In-Reply-To: <CAHrt+GFuOPm1BtC1vNKOagi-kGrvxBgfcy_dsi-KgPwXT8agow@mail.gmail.com>

Hello Louis,

Thanks for your feedback. Please use "reply all" when replying, so that
the mailing list stays in Cc. I've re-added the mailing list in Cc, but
your own reply did not make it to the list.

On Sat, 26 Oct 2019 19:33:28 +0200
Louis Aussedat <aussedat.louis@gmail.com> wrote:

> The post-build.sh script create a folder extlinux and install extlinux.conf
> in it. this line represent the folder and not the conf file.
> I was inspired by orangepi-lite2 config. Maybe it's not the best way to do
> that ?

Ah, I missed that. Seems like what you did is good then. Let me apply
the patch.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-10-26 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 16:44 [Buildroot] [PATCH 1/2] configs/friendlyarm_nanopi_neo_plus2: bump Linux kernel to 5.3.4 and U-Boot to 2019.10 Louis Aussedat
2019-10-26 16:44 ` [Buildroot] [PATCH 2/2] configs/friendlyarm_nanopi_neo_plus2: use an extlinux instead of uEnv.txt Louis Aussedat
2019-10-26 16:57   ` Thomas Petazzoni
     [not found]     ` <CAHrt+GFuOPm1BtC1vNKOagi-kGrvxBgfcy_dsi-KgPwXT8agow@mail.gmail.com>
2019-10-26 18:07       ` Thomas Petazzoni [this message]
2019-10-26 16:57 ` [Buildroot] [PATCH 1/2] configs/friendlyarm_nanopi_neo_plus2: bump Linux kernel to 5.3.4 and U-Boot to 2019.10 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=20191026200708.35ed4e8c@windsurf.home \
    --to=thomas.petazzoni@bootlin.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.