From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] board: Add support for Acmesystems Arietta g25
Date: Thu, 11 Feb 2016 17:26:37 +0100 [thread overview]
Message-ID: <87pow3qkle.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+TH9Vm79Lfi-EH577iDvmnbg2P2vNFV=AwHe6KLSnxcn1Y-EA@mail.gmail.com> (Angelo Compagnucci's message of "Thu, 11 Feb 2016 09:48:12 +0100")
>>>>> "Angelo" == Angelo Compagnucci <angelo.compagnucci@gmail.com> writes:
> Dear Thomas Petazzoni, Peter Korsgaard,
> No way to have it included at this point in time, right?
Strictly no, but it cannot really cause regressions for anything else so
I'll takke a look tonight.
What is the relation between "Arietta g25" and our existing "Aria g25"?
Do we need seperate defconfigs / board support for both?
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-02-11 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 18:08 [Buildroot] [PATCH v3] board: Add support for Acmesystems Arietta g25 Angelo Compagnucci
2016-02-11 8:48 ` Angelo Compagnucci
2016-02-11 16:26 ` Peter Korsgaard [this message]
2016-02-11 16:29 ` Angelo Compagnucci
2016-02-17 15:59 ` Peter Korsgaard
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=87pow3qkle.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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