From: Greg KH <greg@kroah.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Jingoo Han' <jg1.han@samsung.com>,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, gregkh@suse.de,
stern@rowland.harvard.edu, 'Yulgon Kim' <yulgon.kim@samsung.com>,
'Shim Joonyoung' <jy0922.shim@samsung.com>
Subject: Re: Re: [PATCH 0/3] Support Samsung S5P OHCI device and driver
Date: Wed, 21 Dec 2011 10:57:35 -0800 [thread overview]
Message-ID: <20111221185735.GA6609@kroah.com> (raw)
In-Reply-To: <062501ccbf9a$601f3af0$205db0d0$%kim@samsung.com>
On Wed, Dec 21, 2011 at 01:38:24PM +0900, Kukjin Kim wrote:
>
>
> > -----Original Message-----
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Saturday, December 10, 2011 8:58 AM
> > To: Kukjin Kim
> > Cc: 'Jingoo Han'; linux-arm-kernel@lists.infradead.org; linux-
> > usb@vger.kernel.org; linux-samsung-soc@vger.kernel.org; gregkh@suse.de;
> > stern@rowland.harvard.edu; 'Yulgon Kim'; 'Shim Joonyoung'
> > Subject: Re: Re: [PATCH 0/3] Support Samsung S5P OHCI device and driver
> >
> > On Thu, Dec 01, 2011 at 07:10:17PM +0900, Kukjin Kim wrote:
> > > Greg KH wrote:
> > > >
> > > > On Mon, Nov 21, 2011 at 11:57:16AM +0000, Jingoo Han wrote:
> > > > > > -----Original Message-----
> > > > > > From: Greg KH [mailto:greg@kroah.com]
> > > > > > Sent: Friday, November 18, 2011 4:12 AM
> > > > > > To: Jingoo Han
> > > > > > Cc: linux-arm-kernel@lists.infradead.org; linux-
> > usb@vger.kernel.org;
> > > > > > linux-samsung-soc@vger.kernel.org; gregkh@suse.de;
> > > > > > stern@rowland.harvard.edu; kgene.kim@samsung.com;
> > > > yulgon.kim@samsung.com;
> > > > > > jy0922.shim@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
> > > >
> > > Hi Greg,
> > >
> > > Sorry for late response. I came back today from family vacation...
> > >
> > > Anyway,
> > >
> > > > 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.
> > > >
> > > Yes, right. This series would be handled in same tree so that we can
> > avoid
> > > useless conflicts.
> > >
> > > I commented small thing on 3rd patch. So I think, if you're ok on his
> > > updated patch, it can be sent to upstream via Samsung tree. Or your tree
> > > with my ack?
> >
> > The samsung tree is fine to take these, thanks.
> >
> Hi Greg,
>
> OK, let me pick this up in my tree...so, when I apply, may I can have a ack
> from you on 3rd patch?
Yes, feel free to add:
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
prev parent reply other threads:[~2011-12-21 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 11:57 Re: [PATCH 0/3] Support Samsung S5P OHCI device and driver Jingoo Han
2011-11-21 17:23 ` Greg KH
2011-12-01 10:10 ` Kukjin Kim
[not found] ` <046f01ccb011$6d111370$47333a50$%kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2011-12-09 23:58 ` Greg KH
2011-12-21 4:38 ` Kukjin Kim
2011-12-21 18:57 ` Greg KH [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=20111221185735.GA6609@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jg1.han@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=yulgon.kim@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox