From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] out of tree kernel patches question
Date: Sat, 18 Nov 2017 09:26:03 +0100 [thread overview]
Message-ID: <87shdcvvqc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <trinity-0708c540-baa1-463a-a0ad-5bf573ebc7e7-1510991011672@3c-app-mailcom-bs13> (daggs@gmx.com's message of "Sat, 18 Nov 2017 08:43:31 +0100")
>>>>> "daggs" == daggs <daggs@gmx.com> writes:
Hi,
> so I'd like to propose adding a new buildroot config named
> odroidc2-next which will support that along side the existing one.
> with time, hopefully, the old one will be replaced by the new one.
> any objections?
I don't think "next" really explains what this is about, what about
odroidc2_mainline_defconfig?
We have a number of other boards where it may be interesting to do so,
E.G. rpi, roseapplepi, ..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-11-18 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 13:16 [Buildroot] out of tree kernel patches question daggs
2017-11-17 20:24 ` Thomas Petazzoni
2017-11-18 7:43 ` daggs
2017-11-18 8:26 ` Peter Korsgaard [this message]
2017-11-18 12:10 ` daggs
2017-11-20 20:34 ` daggs
2017-11-20 20:50 ` Thomas Petazzoni
2017-11-17 21:33 ` Peter Korsgaard
2017-11-18 7:47 ` daggs
2017-11-18 8:02 ` 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=87shdcvvqc.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