From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [EXT] Re: [PATCH] boot/mv-ddr-marvell: support custom GIT settings
Date: Wed, 26 Dec 2018 14:24:54 +0100 [thread overview]
Message-ID: <20181226142454.59d0bfdf@windsurf.home> (raw)
In-Reply-To: <SN2PR18MB0736322D295DB7F9C1D8DA35CAB50@SN2PR18MB0736.namprd18.prod.outlook.com>
Hello Kostya,
On Wed, 26 Dec 2018 12:33:56 +0000, Kostya Porotchkin wrote:
> [KP] Our intension to add vendor-specific (non-mainlined) components as external packages, which will be based on buildroot build system.
> At some moment they will be public, but will remain vendor-specific and maintained out of the buildroot tree.
I don't think you should make the assumption that those packages will
remain "out of the buildroot tree". As soon as something is publicly
available, there is a chance that someone will be interested in having
it supported as part of upstream Buildroot. So, you shouldn't base your
design on the assumption that this or that package "will remain out of
the Buildroot tree" because this may not be true in the future.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-26 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 13:18 [Buildroot] [PATCH] boot/mv-ddr-marvell: support custom GIT settings kostap at marvell.com
2018-12-24 18:57 ` Yann E. MORIN
2018-12-25 9:09 ` [Buildroot] [EXT] " Kostya Porotchkin
2018-12-26 10:31 ` Thomas Petazzoni
2018-12-26 10:59 ` Kostya Porotchkin
2018-12-26 11:25 ` Yann E. MORIN
2018-12-26 12:33 ` Kostya Porotchkin
2018-12-26 13:24 ` Thomas Petazzoni [this message]
2018-12-26 13:30 ` 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=20181226142454.59d0bfdf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox