From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH 1/2] lttng-modules: Update revision to grab last bugfix releases
Date: Mon, 18 Nov 2013 15:56:17 +0000 [thread overview]
Message-ID: <2012748.zEB8QlG4HV@helios> (raw)
In-Reply-To: <528A32C4.3030306@intel.com>
On Monday 18 November 2013 07:31:16 Saul Wold 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.
FWIW, there is a precedent for this in dylan - I relied upon Bruce sending
patches that he felt were appropriate for the branch, and he did that on at
least one occasion.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-11-18 15:56 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
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 [this message]
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=2012748.zEB8QlG4HV@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox