public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "Hilman, Kevin" <khilman@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"paul@pwsan.com" <paul@pwsan.com>,
	"rmk@arm.linux.org.uk" <rmk@arm.linux.org.uk>
Subject: Re: [PATCH-V5 0/3] Introducing TI's New SoC/board AM335XEVM
Date: Thu, 8 Dec 2011 09:18:54 -0800	[thread overview]
Message-ID: <20111208171854.GB31337@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A8050F6D@DBDE01.ent.ti.com>

Russell,

* Hiremath, Vaibhav <hvaibhav@ti.com> [111208 05:14]:
> > From: Tony Lindgren [mailto:tony@atomide.com]
> > * Kevin Hilman <khilman@ti.com> [111206 15:52]:
> > >
> > > I've also tested it on a BeagleBone, so feel free to also add:
> > >
> > > Tested-by: Kevin Hilman <khilman@ti.com>
> > 
> > Thanks looks good to me. We still need the machine_id update to
> > apply patches 2 and 3 in this series, so applying only the first
> > patch into soc branch for now.
> 
> Tony,
> 
> Should I ping Russell for this? The machine-id patch is already registered
> and present at
> 
> http://www.arm.linux.org.uk/developer/machines/download.php

Care to push the machine_id updates into devel-stable?

Regards,

Tony

  reply	other threads:[~2011-12-08 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  6:43 [PATCH-V5 0/3] Introducing TI's New SoC/board AM335XEVM hvaibhav
2011-12-07  0:24 ` Kevin Hilman
2011-12-07 21:10   ` Tony Lindgren
2011-12-08 13:45     ` Hiremath, Vaibhav
2011-12-08 17:18       ` Tony Lindgren [this message]
2012-02-01  6:53         ` Hiremath, Vaibhav
2012-01-18  8:47     ` Hiremath, Vaibhav

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=20111208171854.GB31337@atomide.com \
    --to=tony@atomide.com \
    --cc=hvaibhav@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rmk@arm.linux.org.uk \
    /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