From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] raspberrypi2: kernel version does no more exist
Date: Fri, 10 Apr 2015 22:21:56 +0200 [thread overview]
Message-ID: <20150410222156.07957902@free-electrons.com> (raw)
In-Reply-To: <55282E0E.8010300@mind.be>
Dear Arnout Vandecappelle,
On Fri, 10 Apr 2015 22:09:50 +0200, Arnout Vandecappelle wrote:
> In that issue, popcornmix writes:
>
> > The stable branches (e.g. 3.18.y) don't get rebased, so should have a linear history
>
> so perhaps we should stick to the stable 3.18 branch instead? The
> raspberry_dt_defconfig is based off the 3.18 branch, so why not do the same for
> the RPi2?
Absolutely. I'm hoping to see some patches about this from our RPi
contributors. Yann? :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-10 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 8:08 [Buildroot] [PATCH] raspberrypi2: kernel version does no more exist Jérôme Pouiller
2015-04-08 8:13 ` Jérôme Pouiller
2015-04-08 21:20 ` Thomas Petazzoni
2015-04-10 20:09 ` Arnout Vandecappelle
2015-04-10 20:21 ` Thomas Petazzoni [this message]
2015-04-28 13:13 ` Frank Hunleth
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=20150410222156.07957902@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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