From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Da Xue <da@lessconfused.com>
Cc: buildroot@buildroot.org, Suniel Mahesh <sunil@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH 1/3] configs/roc_pc_rk3399: remove defconfig
Date: Thu, 3 Nov 2022 11:56:44 +0100 [thread overview]
Message-ID: <20221103115644.4d6abe5c@windsurf> (raw)
In-Reply-To: <CACdvmAh_sHZ3xwmhBa332f5Pg_9c=ZL5BxWbZO3tHn=mRDJJ7g@mail.gmail.com>
Hello Da,
On Wed, 2 Nov 2022 20:03:51 -0400
Da Xue <da@lessconfused.com> wrote:
> This is a Libre Computer only product in the future so the folder is wrong.
> I will re-create in the right folder and maintain these boards in the
> future.
Thanks for your feedback. Should we in the mean time remove the
existing defconfig? Or will you send a patch to fix it up, and rename
what needs to be renamed?
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
next prev parent reply other threads:[~2022-11-03 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 20:18 [Buildroot] [PATCH 0/3] Another small set of defconfig removals Thomas Petazzoni via buildroot
2022-11-02 20:18 ` [Buildroot] [PATCH 1/3] configs/roc_pc_rk3399: remove defconfig Thomas Petazzoni via buildroot
2022-11-03 0:03 ` Da Xue
2022-11-03 10:56 ` Thomas Petazzoni via buildroot [this message]
2022-11-02 20:18 ` [Buildroot] [PATCH 2/3] configs/rock_pi_4: " Thomas Petazzoni via buildroot
2022-11-02 20:18 ` [Buildroot] [PATCH 3/3] configs/rock_pi_n10: " Thomas Petazzoni via buildroot
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=20221103115644.4d6abe5c@windsurf \
--to=buildroot@buildroot.org \
--cc=da@lessconfused.com \
--cc=sunil@amarulasolutions.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