Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.linuxtogo.org
Subject: Re: [PATCH 0/1] Fix "ip route get"
Date: Wed, 8 Jun 2011 23:13:00 +0100	[thread overview]
Message-ID: <201106082313.00702.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4DEFBA1F.9040304@mentor.com>

On Wednesday 08 June 2011 19:06:23 Tom Rini wrote:
> 2.6.38 is current (and in oe.dev), so why not that one?

I guess I was being conservative given we just got burned by upgrading to a 
newer version (well, I say just, it was November IIRC). However if we want to 
bite the bullet and go to 2.6.38 then I'll test & submit a patch to update to 
that.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-06-08 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 13:44 [PATCH 0/1] Fix "ip route get" Paul Eggleton
2011-06-08 13:44 ` [PATCH 1/1] iproute2: update to 2.6.37 Paul Eggleton
2011-06-08 18:06 ` [PATCH 0/1] Fix "ip route get" Tom Rini
2011-06-08 22:13   ` Paul Eggleton [this message]
2011-06-08 22:26     ` Tom Rini

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=201106082313.00702.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.linuxtogo.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox