Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Chien Peter Lin <peterlin@andestech.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: alankao@andestech.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/3] board/andes: rearrange andes folder structure
Date: Wed, 23 Feb 2022 18:09:08 +0800	[thread overview]
Message-ID: <YhYHxAZuz+wY4Nl+@APC323> (raw)
In-Reply-To: <84e159d2-0123-e5b1-c42e-99b70c99f43c@benettiengineering.com>

Hi Giulio,

> On Wed, Feb 23, 2022 at 10:19:08AM +0100, Giulio Benetti wrote:
> > Hi Peter,
> > 
> > On 23/02/22 08:10, Yu Chien Peter Lin wrote:
> > > Rename ae3xx to ae300 for nds32 architecture and add ae350 platform.
> > > 
> > > AE300 (NDS32):
> > > - http://www.andestech.com/en/products-solutions/andeshape-platforms/ae300/
> > > AE350 (RISC-V):
> > > - http://www.andestech.com/en/products-solutions/andeshape-platforms/ae350-axi-based-platform-pre-integrated-with-n25f-nx25f-a25-ax25/
> > > 
> > > Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
> > > Signed-off-by: Alan Kao <alankao@andestech.com>
> > > ---
> > > Changes v1 -> v2:
> > >     - move linux source code and its patches to AndesTech Github repo
> > >     - rename ae350_andestar45_defconfig to andes_ae350_45_defconfig
> > >     - change C library to uClibc
> > >     - remove OpenSSL package
> > >     - remove rootfs.cpio and rootfs.tar
> > >     - update DEVELOPERS
> > > Changes v2 -> v3:
> > >     - specifiy branch to download from AndesTech linux repo
> > >     - change boot.cmd to extlinux.conf
> > >     - add post-build.sh for extlinux.conf to retrieve Image and DTB
> > >     - fix format and update genimage_sdcard.cfg
> > >     - update readme.txt
> > >     - add packages (python3, pylibfdt and openssl) for u-boot binman
> > >     - reorder item in DEVELOPERS
> > > Changes v3 -> v4:
> > >     - rename ae3xx folder to ae300
> > >     - rename andes_ae3xx_defconfig to andes_ae300_defconfig
> > >     - update readme.txt and item in DEVELOPERS
> > 
> > Some of these change ^^^ must have been moved to the single patch, like
> > DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add
> > a --cover-letter, so keep in mind both points for next time.
> > 
> > I've built tested both defconfig successfully, so:
> > Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> > Tested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> > [Giulio: build tested only]
> > 
> > And the other patches of this series is all reviewed, so to me it's ready to
> > be committed, but this will happen after Buildroot 2022.02 is released,
> > since between rc1 to the release Maintainers only accept fixes. Another
> > possibility is that they will commit these patches to next branch.
> > 
> > Please remember to tag V3.
> > 
> > Thank you for your effort!
> > 
> > Best regards
> > -- 
> > Giulio Benetti
> > Benetti Engineering sas

Thanks for reviewing my patches and the guidance.
I will make a new patch for the Config.in,
The last question, is it tag V5 for the next submission?

Regards,
Yu Chien Peter Lin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-02-23 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  7:10 [Buildroot] [PATCH v4 1/3] board/andes: rearrange andes folder structure Yu Chien Peter Lin
2022-02-23  7:10 ` [Buildroot] [PATCH v4 2/3] board/andes/ae350: add support for Andes AE350 Yu Chien Peter Lin
2022-02-23  7:10 ` [Buildroot] [PATCH v4 3/3] DEVELOPERS: add Yu-Chien Lin to board/andes Yu Chien Peter Lin
2022-02-23  9:19 ` [Buildroot] [PATCH v4 1/3] board/andes: rearrange andes folder structure Giulio Benetti
2022-02-23 10:09   ` Yu Chien Peter Lin [this message]
2022-02-23 10:45     ` Giulio Benetti
2022-02-24  2:41       ` Yu Chien Peter Lin
2022-02-24 15:12         ` Giulio Benetti
2022-02-25  8:05           ` Yu Chien Peter Lin

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=YhYHxAZuz+wY4Nl+@APC323 \
    --to=peterlin@andestech.com \
    --cc=alankao@andestech.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.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