From: Yu Chien Peter Lin <peterlin@andestech.com>
To: <thomas.petazzoni@bootlin.com>
Cc: alankao@andestech.com, buildroot@buildroot.org
Subject: [Buildroot] Patch state of andes/ae350
Date: Wed, 9 Feb 2022 11:55:52 +0800 [thread overview]
Message-ID: <YgM7SDj7OxQiOfKt@APC323> (raw)
Hi Thomas,
I would like to follow up on my patches last month.
Are they still under review? Please let me know if
I missed something that needs to be fixed.
Regards,
Yu-Chien Peter Lin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-02-09 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 3:55 Yu Chien Peter Lin [this message]
2022-02-09 22:42 ` [Buildroot] Patch state of andes/ae350 Giulio Benetti
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=YgM7SDj7OxQiOfKt@APC323 \
--to=peterlin@andestech.com \
--cc=alankao@andestech.com \
--cc=buildroot@buildroot.org \
--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