From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Support Samsung S5P OHCI device and driver
Date: Mon, 21 Nov 2011 09:23:44 -0800 [thread overview]
Message-ID: <20111121172344.GA4483@kroah.com> (raw)
In-Reply-To: <33510089.42761321876635907.JavaMail.weblogic@epv6ml08>
On Mon, Nov 21, 2011 at 11:57:16AM +0000, Jingoo Han wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:greg at kroah.com]
> > Sent: Friday, November 18, 2011 4:12 AM
> > To: Jingoo Han
> > Cc: linux-arm-kernel at lists.infradead.org; linux-usb at vger.kernel.org;
> > linux-samsung-soc at vger.kernel.org; gregkh at suse.de;
> > stern at rowland.harvard.edu; kgene.kim at samsung.com; yulgon.kim at samsung.com;
> > jy0922.shim at samsung.com
> > Subject: Re: [PATCH 0/3] Support Samsung S5P OHCI device and driver
> >
> > On Tue, Nov 15, 2011 at 06:49:58AM +0000, Jingoo Han wrote:
> > > Hello.
> > >
> > > This patch series adds USB OHCI device and initial driver for Samsung
> > > S5P SoCs and is based from Linux 3.2-rc1. I have tested on SMDKV310
> > board
> > > using EXYNOS4.
> >
> > This is to be sent through some arm tree, not the usb tree, right?
> Right, 1st and 2nd patch are sent throught arm tree.
> However, 3rd patch is sent through the usb tree.
> Thanks.
> [PATCH 1/3] ARM: SAMSUNG: Add USB OHCI device
> [PATCH 2/3] ARM: EXYNOS: Add USB OHCI support to SMDKV310 board
> [PATCH 3/3] USB: Add S5P OHCI diver
So the third patch does not depend on the first two? If it does, that
means I will get build errors in the USB tree when I apply that patch,
right?
If so, then all three should go through a single tree.
greg k-h
next parent reply other threads:[~2011-11-21 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <33510089.42761321876635907.JavaMail.weblogic@epv6ml08>
2011-11-21 17:23 ` Greg KH [this message]
2011-12-01 10:10 ` [PATCH 0/3] Support Samsung S5P OHCI device and driver Kukjin Kim
2011-12-09 23:58 ` Greg KH
2011-12-21 4:38 ` Kukjin Kim
2011-12-21 18:57 ` Greg KH
2011-11-15 6:49 Jingoo Han
2011-11-17 19:12 ` Greg KH
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=20111121172344.GA4483@kroah.com \
--to=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).