From: Denys Dmytriyenko <denis@denix.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: [RFC][PATCH 1/5] linux-mainline 3.2: kernel recipe based on mainline 3.2.16 with additional patches for e.g. beagleboard on top
Date: Thu, 03 May 2012 13:15:56 -0400 [thread overview]
Message-ID: <20120503171556.GJ2681@denix.org> (raw)
In-Reply-To: <1335899212-29869-1-git-send-email-koen@dominion.thruhere.net>
It's a heavy patch, but my question is - how is it different from linux-3.0 we
already have, besides the version upgrade to 3.2? Why is it called
linux-mainline, the old linux recipe is also mainline with beagle patches.
Basically, I'm trying to understand 2 things here:
- what's the difference between this beagle patch set and the one applied on
top of e.g. 3.0.28? Is it a different dev model, goals, owner or anything else
- why the name change with -mainline suffix?
Other than that it looks fine.
--
Denys
next prev parent reply other threads:[~2012-05-03 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 19:06 [RFC][PATCH 1/5] linux-mainline 3.2: kernel recipe based on mainline 3.2.16 with additional patches for e.g. beagleboard on top Koen Kooi
2012-05-01 19:06 ` [RFC][PATCH 2/5] beagleboard: switch to linux-mainline and drag in more modules Koen Kooi
2012-05-01 19:06 ` [RFC][PATCH 3/5] linux-mainline 3.2: fix build of external SGX modules Koen Kooi
2012-05-01 19:06 ` [RFC][PATCH 4/5] u-boot 2011.12: don't poke at uLCD7 settings from u-boot, it's handled in the kernel now Koen Kooi
2012-05-01 19:23 ` Tom Rini
2012-05-01 19:06 ` [RFC][PATCH 5/5] u-boot 2011.12: switch beagleboard to ext4 to match beaglebone Koen Kooi
2012-05-01 19:23 ` Tom Rini
2012-05-01 19:30 ` Koen Kooi
2012-05-01 20:17 ` Tom Rini
2012-05-03 17:15 ` Denys Dmytriyenko [this message]
2012-05-03 17:20 ` [RFC][PATCH 1/5] linux-mainline 3.2: kernel recipe based on mainline 3.2.16 with additional patches for e.g. beagleboard on top Koen Kooi
2012-05-04 0:12 ` Denys Dmytriyenko
2012-05-04 6:18 ` Koen Kooi
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=20120503171556.GJ2681@denix.org \
--to=denis@denix.org \
--cc=koen@dominion.thruhere.net \
--cc=meta-ti@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.