All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 1/2] USB: OHCI: make ohci-ep93xx a separate driver
Date: Mon, 12 Aug 2013 13:19:19 -0700	[thread overview]
Message-ID: <20130812201919.GA26309@kroah.com> (raw)
In-Reply-To: <1376120501-21368-2-git-send-email-manjunath.goudar@linaro.org>

On Sat, Aug 10, 2013 at 01:11:39PM +0530, Manjunath Goudar wrote:
> Separate the OHCI EP93XX host controller driver from ohci-hcd
> host code so that it can be built as a separate driver module.
> This work is part of enabling multi-platform kernels on ARM.
> 
> Signed-off-by: Manjunath Goudar <manjunath.goudar@linaro.org>
> Signed-off-by: Deepak Saxena <dsaxena@linaro.org>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Greg KH <greg@kroah.com>
> Cc: linux-usb at vger.kernel.org
> 
> V2:
>  -ohci_hcd_init() statements are removed,
>   because by default it is called in ohci_setup().
> 
> V3:
>  -Unused *ohci variable has been removed.
> ---
>  drivers/usb/host/Kconfig       |    8 ++++
>  drivers/usb/host/Makefile      |    1 +
>  drivers/usb/host/ohci-ep93xx.c |   80 +++++++++++++++++-----------------------
>  drivers/usb/host/ohci-hcd.c    |   18 ---------
>  4 files changed, 43 insertions(+), 64 deletions(-)

This too fails to apply:

$ p1 < ../s1
checking file drivers/usb/host/Kconfig
Hunk #1 FAILED at 414.
1 out of 1 hunk FAILED
checking file drivers/usb/host/Makefile
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED
checking file drivers/usb/host/ohci-ep93xx.c
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 120.
Hunk #4 succeeded at 179 (offset -40 lines).
Hunk #5 succeeded@193 (offset -40 lines).
2 out of 5 hunks FAILED
checking file drivers/usb/host/ohci-hcd.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
3 out of 3 hunks ignored


Can you respin _all_ of your pending patches you have sent me in a
format that I can apply them, and resend them in a series that shows
what should be applied in which order.  As it is, I have 3-4 different
series of patches from you, with no obvious order which should be
applied in which order.  Because of that, that might be why these aren't
applying.

thanks,

greg k-h

  reply	other threads:[~2013-08-12 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 17:16 [PATCH 0/2] USB: OHCI: more bus glues as separate modules Manjunath Goudar
2013-07-04 17:16 ` [PATCH 1/2] USB: OHCI: make ohci-ep93xx a separate driver Manjunath Goudar
2013-07-04 20:16   ` Alan Stern
2013-07-04 17:16 ` [PATCH 2/2] USB: OHCI: make ohci-pxa27x " Manjunath Goudar
2013-07-04 20:36   ` Alan Stern
2013-07-26 14:49 ` [PATCH V3 0/2] USB: OHCI: more bus glues as separate modules Manjunath Goudar
2013-07-26 14:49   ` [PATCH V3 1/2] USB: OHCI: make ohci-ep93xx a separate driver Manjunath Goudar
2013-07-26 14:49   ` [PATCH V3 2/2] USB: OHCI: make ohci-pxa27x " Manjunath Goudar
2013-07-26 19:01     ` Alan Stern
2013-08-10  7:41 ` [PATCH V3 0/2] USB: OHCI: more bus glues as separate modules Manjunath Goudar
2013-08-10  7:41   ` [PATCH V3 1/2] USB: OHCI: make ohci-ep93xx a separate driver Manjunath Goudar
2013-08-12 20:19     ` Greg KH [this message]
2013-08-10  7:41   ` [PATCH V3 2/2] USB: OHCI: make ohci-pxa27x " Manjunath Goudar

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=20130812201919.GA26309@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 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.