From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Indrek Kruusa <indrek.kruusa@gmail.com>
Cc: Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] configs/mangopi_mq_d1s: new defconfig
Date: Wed, 9 Aug 2023 22:49:24 +0200 [thread overview]
Message-ID: <20230809224924.5204e05b@windsurf> (raw)
In-Reply-To: <CA+fTLhjjLcwANZ4uatWLQKXq8FObG7-ZOUvpir0bFQVpDZzY+w@mail.gmail.com>
On Wed, 9 Aug 2023 22:40:14 +0300
Indrek Kruusa <indrek.kruusa@gmail.com> wrote:
> > We normally try to have board/<vendor>/<board>/
>
> I was considering that but it's rather tricky for such boards. MangoPi
> boards are manufactured by AWOL (there is a logo on the board
> usually). In fact this is a subsidiary of the Allwinner but I tend to
> think this name doesn't ring a bell for most people. Second, there is
> a website mangopi.org which consolidates information about different
> mangopi boards. So the 'mangopi' could be the "vendor" also... kind
> of. I really don't know what to do about it.
Lets do board/mangopi/mangopi-mq-d1s/ then. We can always revisit later
if need be.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-09 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 17:32 [Buildroot] [PATCH 1/1] configs/mangopi_mq_d1s: new defconfig Indrek Kruusa
2023-08-09 17:35 ` Indrek Kruusa
2023-08-09 17:57 ` Thomas Petazzoni via buildroot
2023-08-09 19:40 ` Indrek Kruusa
2023-08-09 20:49 ` Thomas Petazzoni via buildroot [this message]
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=20230809224924.5204e05b@windsurf \
--to=buildroot@buildroot.org \
--cc=indrek.kruusa@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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