From: Samuel Ortiz <sameo@linux.intel.com>
To: Roger Quadros <rogerq@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"Balbi, Felipe" <balbi@ti.com>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] mfd: OMAP USB Host cleanup for 3.9
Date: Thu, 14 Feb 2013 13:26:20 +0100 [thread overview]
Message-ID: <20130214122620.GF20996@sortiz-mobl> (raw)
In-Reply-To: <511CD26F.4080909@ti.com>
Hi Roger
On Thu, Feb 14, 2013 at 02:02:55PM +0200, Roger Quadros wrote:
> Hi Samuel,
>
> This contains the MFD portion of the OMAP USB Host cleanup series for 3.9.
> It is based on 3.8-rc6 + usbhost17-common that I've sent earlier.
>
> The first patch touches drivers/usb/ehci-omap.c and is pending ACK from Greg KH.
> The reason it needs to go through MFD tree is that it depends on the platform
> header changes as the MFD drivers.
>
> Please pull. Thanks.
>
> The following changes since commit 7f07863ec60f7d3dbeec5aff881ea074db3925ed:
>
> ARM: OMAP: Consolidate OMAP USB-HS platform data (part 1/3) (2013-02-13 13:22:34 +0200)
>
> are available in the git repository at:
> git://github.com/rogerq/linux.git usbhost17-for-mfd
Pulled as well, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] mfd: OMAP USB Host cleanup for 3.9
Date: Thu, 14 Feb 2013 13:26:20 +0100 [thread overview]
Message-ID: <20130214122620.GF20996@sortiz-mobl> (raw)
In-Reply-To: <511CD26F.4080909@ti.com>
Hi Roger
On Thu, Feb 14, 2013 at 02:02:55PM +0200, Roger Quadros wrote:
> Hi Samuel,
>
> This contains the MFD portion of the OMAP USB Host cleanup series for 3.9.
> It is based on 3.8-rc6 + usbhost17-common that I've sent earlier.
>
> The first patch touches drivers/usb/ehci-omap.c and is pending ACK from Greg KH.
> The reason it needs to go through MFD tree is that it depends on the platform
> header changes as the MFD drivers.
>
> Please pull. Thanks.
>
> The following changes since commit 7f07863ec60f7d3dbeec5aff881ea074db3925ed:
>
> ARM: OMAP: Consolidate OMAP USB-HS platform data (part 1/3) (2013-02-13 13:22:34 +0200)
>
> are available in the git repository at:
> git://github.com/rogerq/linux.git usbhost17-for-mfd
Pulled as well, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-02-14 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 12:01 [GIT PULL] common: OMAP USB Host cleanup for 3.9 Roger Quadros
2013-02-14 12:01 ` Roger Quadros
2013-02-14 12:02 ` [GIT PULL] mfd: " Roger Quadros
2013-02-14 12:26 ` Samuel Ortiz [this message]
2013-02-14 12:26 ` Samuel Ortiz
2013-02-14 12:04 ` [GIT PULL] arm-soc: " Roger Quadros
2013-02-14 16:48 ` Tony Lindgren
2013-02-14 16:48 ` Tony Lindgren
2013-02-14 12:25 ` [GIT PULL] common: " Samuel Ortiz
2013-02-14 12:25 ` 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=20130214122620.GF20996@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.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.