All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH] Fix use of PRINC in meta-intel BSPs
Date: Tue, 09 Oct 2012 20:07:39 -0700	[thread overview]
Message-ID: <5074E67B.1050103@linux.intel.com> (raw)
In-Reply-To: <ADD6A3980E8C39419A432FF422031B4C1573101E@ORSMSX106.amr.corp.intel.com>

On 10/09/2012 06:10 PM, Kamble, Nitin A wrote:
> Tested this for sugarbay BSP, and did not see any issues with it.

Thanks for the additional testing Nitin, much appreciated.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


      reply	other threads:[~2012-10-10  3:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 22:53 [PATCH 0/1][meta-intel] Fix use of PRINC in meta-intel BSPs Darren Hart
2012-10-09 22:53 ` [PATCH] " Darren Hart
2012-10-09 23:00   ` Tom Zanussi
2012-10-10  1:10   ` Kamble, Nitin A
2012-10-10  3:07     ` Darren Hart [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=5074E67B.1050103@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=nitin.a.kamble@intel.com \
    --cc=yocto@yoctoproject.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 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.