From: Greg KH <greg@kroah.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"ss@aao.gov.au" <ss@aao.gov.au>, Greg KH <gregkh@suse.de>
Subject: Re: [PATCH v2] Staging: dt3155: Cleanup memory mapped i/o access
Date: Tue, 22 Jun 2010 16:04:28 -0700 [thread overview]
Message-ID: <20100622230428.GA2854@kroah.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269763716504D6@AUSP01VMBX24.collaborationhost.net>
On Tue, Jun 22, 2010 at 05:45:32PM -0500, H Hartley Sweeten wrote:
> On Tuesday, June 22, 2010 3:39 PM, Greg KH wrote:
> > You are still doing something odd, this one doesn't apply either. Is
> > your email client messing something up?
> >
> > strange.
>
> Hmm. I thought I had that worked out since I haven't had any problems lately.
>
> Can you please try this one?
Nope, I get the following errors:
>tching file drivers/staging/dt3155/dt3155_drv.c
Hunk #2 FAILED at 112.
Hunk #7 succeeded at 214 with fuzz 2.
Hunk #8 succeeded at 234 with fuzz 2.
Hunk #9 FAILED at 252.
Hunk #10 succeeded at 260 with fuzz 2.
Hunk #12 succeeded at 313 with fuzz 2.
Hunk #13 FAILED at 390.
Hunk #14 succeeded at 405 with fuzz 2.
Hunk #16 FAILED at 433.
Hunk #17 FAILED at 451.
Hunk #22 succeeded at 915 with fuzz 1.
Hunk #23 succeeded at 1040 with fuzz 2.
5 out of 23 hunks FAILED -- saving rejects to file drivers/staging/dt3155/dt3155_drv.c.rej
patching file drivers/staging/dt3155/dt3155_drv.h
patching file drivers/staging/dt3155/dt3155_io.c
Hunk #2 FAILED at 77.
Hunk #3 FAILED at 103.
Hunk #4 FAILED at 119.
Hunk #5 FAILED at 134.
Hunk #6 FAILED at 151.
5 out of 6 hunks FAILED -- saving rejects to file drivers/staging/dt3155/dt3155_io.c.rej
patching file drivers/staging/dt3155/dt3155_io.h
Reversed (or previously applied) patch detected! Assume -R? [n]
not good...
thanks,
greg k-h
next prev parent reply other threads:[~2010-06-22 23:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 17:23 [PATCH] Staging: dt3155: Cleanup memory mapped i/o access H Hartley Sweeten
2010-04-30 21:56 ` Greg KH
2010-05-02 17:35 ` H Hartley Sweeten
2010-05-02 18:00 ` H Hartley Sweeten
2010-05-03 18:59 ` Greg KH
2010-05-03 20:15 ` H Hartley Sweeten
2010-05-03 21:17 ` Greg KH
2010-05-03 22:24 ` H Hartley Sweeten
2010-05-03 22:45 ` H Hartley Sweeten
2010-05-03 23:33 ` H Hartley Sweeten
2010-05-03 23:40 ` Greg KH
2010-05-03 23:41 ` Greg KH
2010-05-03 23:59 ` Joe Perches
2010-05-04 2:54 ` Greg KH
2010-05-04 19:07 ` Joe Perches
2010-05-04 20:02 ` H Hartley Sweeten
2010-05-04 20:12 ` Greg KH
2010-05-04 20:53 ` H Hartley Sweeten
2010-05-04 21:02 ` Greg KH
2010-05-04 21:22 ` H Hartley Sweeten
2010-05-06 16:59 ` H Hartley Sweeten
2010-05-06 20:25 ` Greg KH
2010-06-21 15:51 ` [PATCH v2] " H Hartley Sweeten
2010-06-22 22:39 ` Greg KH
2010-06-22 22:45 ` H Hartley Sweeten
2010-06-22 23:04 ` Greg KH [this message]
2010-06-22 23:36 ` H Hartley Sweeten
2010-05-04 0:49 ` H Hartley Sweeten
-- strict thread matches above, loose matches on Subject: below --
2010-06-22 23:38 [PATCH v2] " H Hartley Sweeten
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=20100622230428.GA2854@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ss@aao.gov.au \
/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.