public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Kevin Hilman <khilman@ti.com>
Cc: "Munegowda, Keshava" <keshava_mgowda@ti.com>,
	Russ Dill <Russ.Dill@ti.com>, Anatolij Gustschin <agust@denx.de>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] Fix build breakage in omap-usb-host.c
Date: Mon, 30 Apr 2012 10:22:22 +0200	[thread overview]
Message-ID: <20120430082222.GA31528@sortiz-mobl> (raw)
In-Reply-To: <87ty0452ur.fsf@ti.com>

Hi Kevin,

On Fri, Apr 27, 2012 at 01:36:28PM -0700, Kevin Hilman wrote:
> Samuel,
> 
> "Munegowda, Keshava" <keshava_mgowda@ti.com> writes:
> 
> > On Sun, Apr 22, 2012 at 2:20 PM, Russ Dill <Russ.Dill@ti.com> wrote:
> >> On Sun, Apr 22, 2012 at 1:48 AM, Russ Dill <Russ.Dill@ti.com> wrote:
> >>> 'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue' removes the include for
> >>> linux/gpio.h from omap-usb-host.c. This include indirectly includes plat/cpu.h
> >>> which is required by omap-usb-host.c. Fix the build breakage by including
> >>> it directly.
> >>
> >> (Sorry, I should add some detail, this is a build breakage in linux-next)
> >
> > Russ Dill and Anatolij Gustschin
> >
> > Both patches fixes the same issue; But here , I am seeing Russ Dill
> > has sent earlier (in my mailbox it shows 21 hours ago)
> > Here my ack by:
> >
> > Acked-by:  Keshava Munegowda <keshava_mgowda@ti.com>
> 
> Acked-by: Kevin Hilman <khilman@ti.com>
> 
> Can you pick this up for v3.4-rc5?  The breakage was introduced in
> v3.4-rc4.
I will, yes.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  parent reply	other threads:[~2012-04-30  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22  8:48 [PATCH] Fix build breakage in omap-usb-host.c Russ Dill
2012-04-22  8:50 ` Russ Dill
2012-04-23  6:25   ` Munegowda, Keshava
2012-04-23 18:49     ` Anatolij Gustschin
     [not found]     ` <87ty0452ur.fsf@ti.com>
2012-04-30  8:22       ` Samuel Ortiz [this message]
2012-05-01  9:56 ` Samuel Ortiz

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=20120430082222.GA31528@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=Russ.Dill@ti.com \
    --cc=agust@denx.de \
    --cc=keshava_mgowda@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.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