From: Denys Dmytriyenko <denys@ti.com>
To: "Sixten Sjöström Thames" <Sixten.Sjoestroem.Thames@enea.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
"santosh.shilimkar@ti.com" <santosh.shilimkar@ti.com>
Subject: Re: NO_HZ and TI MCSDK 3.8.4 kernel for Keystone 2
Date: Thu, 26 Sep 2013 13:36:26 -0400 [thread overview]
Message-ID: <20130926173626.GY14528@edge> (raw)
In-Reply-To: <B0B361514883EA47B19C4FC8275640D125BC8137@sestoex09.enea.se>
In general, you need to subscribe to the mailing list to be able to post to
it. But in this case, meta-arago is probably not the right list for you - are
you trying to build an Arago distribution that is based on OpenEmbedded and
the Yocto Project? If it's just the kernel question, then Santosh should be
able to help you or point you in the right direction. Thanks.
On Wed, Sep 25, 2013 at 12:47:58PM +0000, Sixten Sjöström Thames wrote:
> Hi,
>
> I'm interested in getting the CONFIG_NO_HZ_FULL kernel configuration
> (http://lwn.net/Articles/549580/) to work with the MCSDK kernel for Keystone
> 2 (http://arago-project.org/git/projects/?p=linux-keystone.git).
>
> Some questions: Are there any plans to rebase the Keystone 2 BSP against a
> newer Linux kernel version that supports NO_HZ_FULL (3.10 or later) in the
> near future? Are there any available patches that enable the NO_HZ_FULL
> configuration for the MCSDK 3.8.4 Linux kernel?
>
> Best Regards,
> Sixten Sjöström Thames
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
next prev parent reply other threads:[~2013-09-26 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 12:47 NO_HZ and TI MCSDK 3.8.4 kernel for Keystone 2 Sixten Sjöström Thames
2013-09-26 17:36 ` Denys Dmytriyenko [this message]
2013-09-26 17:56 ` Santosh Shilimkar
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=20130926173626.GY14528@edge \
--to=denys@ti.com \
--cc=Sixten.Sjoestroem.Thames@enea.com \
--cc=meta-arago@arago-project.org \
--cc=santosh.shilimkar@ti.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.