From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Yu Chien Peter Lin <peterlin@andestech.com>
Cc: Alan Kao <alankao@andestech.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] board/andes: rearrange nds32 folder structure
Date: Tue, 11 Jan 2022 21:13:16 +0100 [thread overview]
Message-ID: <20220111211316.7f94cb45@windsurf> (raw)
In-Reply-To: <20220111035859.12895-1-peterlin@andestech.com>
Hello Yu,
On Tue, 11 Jan 2022 11:58:58 +0800
Yu Chien Peter Lin <peterlin@andestech.com> wrote:
> Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
> Signed-off-by: Alan Kao <alankao@andestech.com>
> ---
> .../patches/linux/0001-nds32-Fix-boot-messages-garbled.patch | 0
> board/andes/{ => ae3xx}/readme.txt | 0
> configs/andes_ae3xx_defconfig | 2 +-
> 3 files changed, 1 insertion(+), 1 deletion(-)
> rename board/andes/{ => ae3xx}/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch (100%)
> rename board/andes/{ => ae3xx}/readme.txt (100%)
Thanks for your patch. However, I am a bit confused, because after your
two patches, we will have:
board/andes/ae3xx/ => the NDS32 platform
board/andes/ae350/ => the RISC-V platform
but the ae3xx wildcard matches ae350, so it feels really odd.
Could you clarify?
Best regards,
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:[~2022-01-11 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 3:58 [Buildroot] [PATCH 1/2] board/andes: rearrange nds32 folder structure Yu Chien Peter Lin
2022-01-11 3:58 ` [Buildroot] [PATCH 2/2] board/andes/ae350: add support for Andes AE350 Yu Chien Peter Lin
2022-01-11 20:21 ` Thomas Petazzoni
2022-01-11 20:13 ` Thomas Petazzoni [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=20220111211316.7f94cb45@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=alankao@andestech.com \
--cc=buildroot@buildroot.org \
--cc=peterlin@andestech.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