All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: dvhart@linux.intel.com, linux-yocto@yoctoproject.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] linux-yocto: consolidated pull request
Date: Wed, 05 Dec 2012 16:27:53 +0000	[thread overview]
Message-ID: <1354724873.25268.119.camel@ted> (raw)
In-Reply-To: <1354723571.1715.17.camel@empanada>

On Wed, 2012-12-05 at 10:06 -0600, Tom Zanussi wrote:
> On Wed, 2012-12-05 at 15:48 +0000, Burton, Ross wrote:
> > On 21 November 2012 21:32, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
> > > atom-pc should probably be using the 3.4 kernel, but that's a
> > > question for Darren/Tom/Nitin (so I've added them to the cc), since
> > > there may be a reason (with respect to graphics) as to why it is on
> > > 3.0.
> > 
> > Ping Darren/Tom/Nitin.
> > 
> > atom-pc is certainly lagging behind by still being on 3.0, and I can't
> > see any reason why we'd want to stick with 3.0 for graphics.  In fact
> > as the most common graphics driver used on atom-pc is a i965 we want a
> > modern kernel as that is where the development is.
> > 
> 
> I don't know of any technical reason for it to still be at 3.0.
> 
> Until recently all of the 'core machines' were at 3.0 and probably the
> assumption was that whoever upgraded those in the past would also be
> upgrading atom-pc - has that changed?.
> 
> So who does own the core machines and if that doesn't cover atom-pc,
> then who owns that?

As I understood it, WR owns the non-IA core machines, you (as in the
Intel team) own the IA ones, namely atom-pc.

Cheers,

Richard




  reply	other threads:[~2012-12-05 16:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 21:32 [PATCH 0/4] linux-yocto: consolidated pull request Bruce Ashfield
2012-11-21 21:32 ` [PATCH 1/4] linux-yocto/3.0: fix virtio configuration typo Bruce Ashfield
2012-11-21 21:32 ` [PATCH 2/4] linux-yocto/3.4: uprobes: reinstate config options for 'uprobe' feature Bruce Ashfield
2012-11-21 21:32 ` [PATCH 3/4] kernel-yocto: clarify KMETA branch comments Bruce Ashfield
2012-11-21 21:32 ` [PATCH 4/4] kern-tools: report missing config fragments by name Bruce Ashfield
2012-12-05 15:48 ` [PATCH 0/4] linux-yocto: consolidated pull request Burton, Ross
2012-12-05 16:06   ` Tom Zanussi
2012-12-05 16:27     ` Richard Purdie [this message]
2012-12-05 16:51       ` Darren Hart
2012-12-05 16:57       ` Tom Zanussi
  -- strict thread matches above, loose matches on Subject: below --
2022-02-13  1:23 bruce.ashfield
2021-06-27 14:13 Bruce Ashfield
2021-01-12 22:14 Bruce Ashfield
2019-03-01  5:34 bruce.ashfield
2015-09-29 14:31 Bruce Ashfield
2014-02-27 21:12 Bruce Ashfield
2013-11-04  5:56 Bruce Ashfield
2013-06-26 13:40 Bruce Ashfield
2012-07-03 15:14 Bruce Ashfield
2012-07-05 17:44 ` Saul Wold
2011-12-22 18:05 Bruce Ashfield
2012-01-03 21:14 ` Saul Wold

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=1354724873.25268.119.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dvhart@linux.intel.com \
    --cc=linux-yocto@yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tom.zanussi@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.