From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Saul Wold <saul.wold@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases
Date: Mon, 18 Nov 2013 10:59:38 -0500 [thread overview]
Message-ID: <528A396A.6020500@windriver.com> (raw)
In-Reply-To: <CAP9ODKqrKrqWPg6ZCnM715RLjjRJ3satfm3ouOwWmpt+ygBU_A@mail.gmail.com>
On 13-11-18 10:50 AM, Otavio Salvador wrote:
> On Mon, Nov 18, 2013 at 1:31 PM, Saul Wold <saul.wold@intel.com> wrote:
>> On 11/18/2013 06:50 AM, Robert Yang wrote:
>>>
>>>
>>> On 11/18/2013 10:18 PM, Otavio Salvador wrote:
>>>>
>>>> On Mon, Nov 18, 2013 at 10:25 AM, Robert Yang
>>>> <liezhi.yang@windriver.com> wrote:
>>>>>>
>>>>>>
>>>>>> This should be considered for Dora as well as it fixes the deadlock
>>>>>> and building with 3.12 kernels.
>>>>>>
>>>>>
>>>>> Hi Otavio, thanks for suggesting this for dora, but dora's kernel is
>>>>> 3.10.11,
>>>>> and this is an update for lttng-modules, I'm not sure whether dora needs
>>>>> this.
>>>>>
>>>>> Add Saul in the CC list.
>>>>
>>>>
>>>> I think Dora ought to get the new 3.10 kernel updates; this can go
>>>> along side with it.
>>>>
>>>
>>> Hi Otavio,
>>>
>>> I'm sorry, but I'm not sure whether we need update dora's kernel from
>>> 3.10.11
>>> to 3.10.17, since we seldom do the package update for a stable branch,
>>> let's wait for others' comments:-).
>>>
>> This is correct, I do not think we will be updating the kernel for a stable
>> branch.
>
> This is wrong. We should update to 3.10.17 as this is the LTS release,
> otherwise what is the point of us using a LTS at all?
Obviously I'll be maintaining the LTS release in master, but that
maintenance gets a mix of bug fixes and features associated with the
upstream maintenance + LTSI + BSP requirements.
I've sent patches for the sustained branches in the past, and can
do it here as well. But to do it properly, there really needs to be a
dedicated kernel repository, since things like the LTSI import and
new BSP support will be mixed into the tree if a single 3.10 repo
is used.
I'm willing to split the repo and do -stable korg release updates, but
at some point there are only so many repositories and versions that
should be maintained at one time. As to what that number is, I don't have
a firm one in mind.
At a minimum, it would be safe for the dora maintenance branch to take
my latest kernel -stable imports, but in the not to distant future,
it would need a separate maintenance stream.
Cheers,
Bruce
>
next prev parent reply other threads:[~2013-11-18 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 13:31 [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases Otavio Salvador
2013-11-01 13:31 ` [PATCH 2/2] lttng-modules: Backport fixes to allow use with 3.12 kernels Otavio Salvador
2013-11-13 21:54 ` [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases Saul Wold
2013-11-14 1:45 ` Otavio Salvador
2013-11-14 3:08 ` Bruce Ashfield
2013-11-14 16:09 ` Saul Wold
2013-11-14 16:18 ` Bruce Ashfield
2013-11-14 17:15 ` Bruce Ashfield
2013-11-14 17:48 ` Otavio Salvador
2013-11-18 12:25 ` Robert Yang
2013-11-18 14:18 ` Otavio Salvador
2013-11-18 14:50 ` Robert Yang
2013-11-18 15:31 ` Saul Wold
2013-11-18 15:50 ` Otavio Salvador
2013-11-18 15:59 ` Bruce Ashfield [this message]
2013-11-19 3:34 ` Robert Yang
2013-11-19 5:18 ` Bruce Ashfield
2013-11-21 3:05 ` Robert Yang
2013-11-21 6:05 ` Bruce Ashfield
2013-11-18 15:56 ` Paul Eggleton
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=528A396A.6020500@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.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 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.