From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] uboot-tools: bump to version 2016.09
Date: Thu, 15 Sep 2016 08:31:28 +0200 [thread overview]
Message-ID: <1473921088.3151.7.camel@embedded.rocks> (raw)
In-Reply-To: <CAOMZO5Bp_dctdOw_WrYOjNRh6dAaTb-0Lqu1YSRJUitwy5+o8g@mail.gmail.com>
Hi Fabio,
On Di, 2016-09-13 at 12:02 -0300, Fabio Estevam wrote:
> Hi J?rg,
>
> On Mon, Sep 12, 2016 at 5:42 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> >
> > Hello,
> >
> > On Mon, 12 Sep 2016 14:03:41 -0300, Fabio Estevam wrote:
> > >
> > > From: Fabio Estevam <fabio.estevam@nxp.com>
> > >
> > > Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> > > ---
> > > ?.../uboot-tools/0002-tools-only-in-no-dot-config-targets.patch |
> > > 10 ++++++----
> >
> > It would be nice if one day, someone upstreamed this patch, in this
> > form or another.
>
> Would like to understand from you if you have ever made an attempt to
> upstream uboot-tools/0002-tools-only-in-no-dot-config-targets.patch.
It's been a while since the patch was applied, but I try to remember.
This [1] is the corresponding patch from U-Boot. And googeling through the U-boot mailing list I do not find anything regarding this issue.
> Is this something that you could submit to the U-Boot list to get
> some feedback?
I can try.
[1]?http://lists.denx.de/pipermail/u-boot/2014-October/191526.html
Best regards
J?rg Krause
next prev parent reply other threads:[~2016-09-15 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 17:03 [Buildroot] [PATCH 1/2] boot/uboot: bump to version 2016.09 Fabio Estevam
2016-09-12 17:03 ` [Buildroot] [PATCH 2/2] uboot-tools: " Fabio Estevam
2016-09-12 20:42 ` Thomas Petazzoni
2016-09-12 20:45 ` Fabio Estevam
2016-09-13 15:02 ` Fabio Estevam
2016-09-15 6:31 ` Jörg Krause [this message]
2016-09-15 23:23 ` Fabio Estevam
2016-09-12 20:41 ` [Buildroot] [PATCH 1/2] boot/uboot: " 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=1473921088.3151.7.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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.