From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] {Makefile,config.mk,a/Kconfig}: introduce SUPPLIER
Date: Thu, 13 Feb 2020 10:01:23 -0500 [thread overview]
Message-ID: <20200213150123.GI18302@bill-the-cat> (raw)
In-Reply-To: <20200213133353.20353-1-sno@netbsd.org>
On Thu, Feb 13, 2020 at 02:33:53PM +0100, Jens Rehsack wrote:
> From: Jens Rehsack <sno@NetBSD.org>
>
> Introduce SUPPLIER analogous to VENDOR to allow (from customer perspective)
> a VENDOR using it's SUPPLIER's common/ code.
>
> This is reasonable, when a VENDOR (from customer perspective) builds
> several machines sharing some features (e.g. some FPGA which has to be
> initialized during u-boot) but wants to use common NXP or Samsung code
> for the BSP instead of copying and create merge overhead.
>
> Signed-off-by: Jens Rehsack <sno@NetBSD.org>
> ---
> Makefile | 4 +++-
> arch/Kconfig | 12 ++++++++++++
> config.mk | 6 +++++-
> 3 files changed, 20 insertions(+), 2 deletions(-)
Can you provide a follow-up where this it clearer / easier to do
something than today? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200213/07b85629/attachment.sig>
next prev parent reply other threads:[~2020-02-13 15:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 13:33 [PATCH] {Makefile,config.mk,a/Kconfig}: introduce SUPPLIER Jens Rehsack
2020-02-13 15:01 ` Tom Rini [this message]
2020-02-13 16:57 ` Jens Rehsack
2020-02-13 17:48 ` Tom Rini
2020-02-14 9:36 ` Michal Simek
2020-02-14 11:37 ` Jens Rehsack
2020-02-14 11:49 ` Michal Simek
2020-02-14 13:45 ` Tom Rini
2020-02-14 14:21 ` Jens Rehsack
2020-02-14 14:28 ` Tom Rini
2020-02-14 14:40 ` Jens Rehsack
2020-02-14 14:43 ` Tom Rini
2020-02-14 15:20 ` Jens Rehsack
2020-02-17 9:42 ` Michal Simek
2020-02-14 12:08 ` Fabio Estevam
2020-02-14 12:22 ` Jens Rehsack
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=20200213150123.GI18302@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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