Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Marek Szyprowski
	<m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
Subject: Re: s3c-hsotg patches
Date: Thu, 15 Jul 2010 03:05:54 -0700	[thread overview]
Message-ID: <20100715100554.GA12786@kroah.com> (raw)
In-Reply-To: <20100715090222.GD16584-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>

On Thu, Jul 15, 2010 at 10:02:22AM +0100, Ben Dooks wrote:
> On Wed, Jul 14, 2010 at 08:10:26AM -0700, Greg KH wrote:
> > On Wed, Jul 14, 2010 at 11:39:50AM +0200, Marek Szyprowski wrote:
> > > Hello,
> > > 
> > > On Wednesday, July 07, 2010 5:13 PM Greg KH wrote:
> > > 
> > > > On Wed, Jul 07, 2010 at 01:02:12AM +0100, Ben Dooks wrote:
> > > > > Re-send of previous set, with corrected patches.
> > > > 
> > > > Hm, what tree are these going through?  Do you need me to take them
> > > > through the linux-usb tree?  Or are they going through a
> > > > platform-specific one somewhere?
> > > > 
> > > > confused,
> > > 
> > > Looks that Ben is busy and has no time to answer...
> > 
> > Then we all should be too busy to apply them :)
> 
> I've been really ill for the last couple of weeks, so still sifting
> through a pile of stuff that needs to be sorted.

Completly understandable, the comment "no time to answer" I took to be a
choice on your part, not external circumstances, my appologies.  Hope
you are better now.

> They where sent to you as I much prefer the driver specific stuff to go
> to the relevant maintainer and if possible have them merged via the
> maintainer tree.

Great.

> > Seriously, if a simple question like this is ignored, what happens if a
> > real problem is reported?
> > 
> > > I'm interested in merging these patches too. These patches were
> > > intended to be merged to 2.6.35-rc5. They are available on 
> > > git://git.fluff.org/bjdooks/linux for-2635-rc5/hsotg branch.
> > > 
> > > IMHO these patches should go though the linux-usb tree - they
> > > don't touch any platform specific code, and register definitions 
> > > (arch/arm/plat-samsung/include/plat/regs-usb-hsotg.h) in fact belongs
> > > to the driver rather than the platform. s3c-hsotg driver belongs to
> > > the linux-usb tree.
> > 
> > Ok, I can take them all, care to resend them through email?
> 
> Do you still want them re-sending. I'd have to check that the branch
> on git://git.fluff.org/bjdooks/linux for-2635-rc5/hsotg is up to date
> before having it pulled.

I can't "pull" trees, sorry, I need email patches.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-07-15 10:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  0:02 s3c-hsotg patches Ben Dooks
2010-07-07  0:02 ` [PATCH 01/11] USB: s3c-hsotg: Increase TX fifo limit Ben Dooks
2010-07-07  0:02 ` [PATCH 02/11] USB: s3c-hsotg: The NPTX/PTX FIFO sizes are in words, not bytes Ben Dooks
2010-07-07  0:02 ` [PATCH 03/11] USB: s3c-hsotg: Avoid overwriting contents of perodic in 'fifo' Ben Dooks
     [not found] ` <1278460943-16224-1-git-send-email-ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
2010-07-07  0:02   ` [PATCH 04/11] USB: s3c-hsotg: Re-initialise all FIFOs on USB bus reset Ben Dooks
2010-07-07  0:02   ` [PATCH 06/11] USB: s3c-hsotg: Only load packet per fifo write Ben Dooks
2010-07-09 10:48     ` Sergei Shtylyov
2010-07-07  0:02   ` [PATCH 08/11] USB: s3c-hsotg: Fix max EP0 IN request length Ben Dooks
2010-07-07  0:02 ` [PATCH 05/11] USB: s3c-hsotg: Add initial detection and setup for dedicated FIFO mode Ben Dooks
2010-07-07  0:02 ` [PATCH 07/11] USB: s3c-hsotg: Check for new request before enqueing new setup Ben Dooks
2010-07-07  0:02 ` [PATCH 09/11] USB: s3c-hsotg: Fix the OUT EP0 limit Ben Dooks
2010-07-07  0:02 ` [PATCH 10/11] USB: s3c-hsotg: Fix OUT packet request retry Ben Dooks
2010-07-07  0:02 ` [PATCH 11/11] USB: s3c-hsotg: Add support for external USB clock Ben Dooks
2010-07-07 15:12 ` s3c-hsotg patches Greg KH
2010-07-14  9:39   ` Marek Szyprowski
     [not found]     ` <00c401cb2338$84a3f730$8debe590$%szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-07-14 15:10       ` Greg KH
     [not found]         ` <20100714151026.GD24104-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2010-07-15  9:02           ` Ben Dooks
     [not found]             ` <20100715090222.GD16584-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-07-15 10:05               ` 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=20100715100554.GA12786@kroah.com \
    --to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.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