All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Yu Chien Peter Lin <peterlin@andestech.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/3] board/andes/ae350: add support for Andes AE350
Date: Wed, 16 Feb 2022 02:52:37 +0100	[thread overview]
Message-ID: <40D75C1A-19A7-4E03-8B69-976F680BE842@benettiengineering.com> (raw)
In-Reply-To: <YgxKvW3ab+JbmYA/@APC323>


> Il giorno 16 feb 2022, alle ore 01:53, Yu Chien Peter Lin <peterlin@andestech.com> ha scritto:
> 
> Hi Giulio,
> 
>>> On Tue, Feb 15, 2022 at 02:00:36PM +0100, Giulio Benetti wrote:
>>> Hi Peter,
>>> 
>>>> Il giorno 15 feb 2022, alle ore 06:16, Yu Chien Peter Lin <peterlin@andestech.com> ha scritto:
>>>> 
>>>> 
>>>>> 
>>>>>> On Tue, Feb 15, 2022 at 10:32:01AM +0800, Yu Chien Peter Lin wrote:
>>>>>> This patch provides defconfig and basic support for the Andes
>>>>>> 45 series RISC-V architecture.
>>>>>> 
>>>>>> 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
>>>>>> 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
>>>>>> 
>>>> 
>>>> Sorry, I missed versioning for this revision.
>>>> I'll resend it and fix changelog format.
>>> 
>>> Can you please subscribe to patchwork[1] and tag your patches without V3 prefix as rejected?
>>> 
>>> [1]: https://patchwork.ozlabs.org/project/buildroot/list/
>>> 
>>> Thank you!
>>> Giulio
> 
> Sure, I've updated. Sorry about that.

No problem, please also the v2 version.
You can filter by your name and check your patches.

Thank you!

Best regards
Giulio

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

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-02-16  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  2:32 [Buildroot] [PATCH 1/3] board/andes: rearrange nds32 folder structure Yu Chien Peter Lin
2022-02-15  2:32 ` [Buildroot] [PATCH 2/3] board/andes/ae350: add support for Andes AE350 Yu Chien Peter Lin
2022-02-15  5:14   ` Yu Chien Peter Lin
2022-02-15 13:00     ` Giulio Benetti
2022-02-16  0:52       ` Yu Chien Peter Lin
2022-02-16  1:52         ` Giulio Benetti [this message]
2022-02-21 19:10   ` Giulio Benetti
2022-02-15  2:32 ` [Buildroot] [PATCH 3/3] DEVELOPERS: add Yu-Chien Lin to board/andes 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=40D75C1A-19A7-4E03-8B69-976F680BE842@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.