From: "Freels, James D." <freelsjd@ornl.gov>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: bugme-daemon@bugzilla.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 8366] aic79xx and aic7xxx driver issues
Date: Thu, 26 Jul 2007 17:52:17 -0400 [thread overview]
Message-ID: <1185486737.14419.73.camel@fea.ornl.gov> (raw)
In-Reply-To: <1185486264.3501.99.camel@localhost.localdomain>
Thanks James. It patched this time, compiled, and is now rebooting. I
have a backup running tonight at 1am. I will report back in.
This would be great if it fixes it. I also have another similar bug
with the aic79xx driver on another machine (see my other bug reports).
I wonder if this will fix it also ?
On Thu, 2007-07-26 at 17:44 -0400, James Bottomley wrote:
> On Thu, 2007-07-26 at 17:37 -0400, Freels, James D. wrote:
> > Here is what I get when I apply the patch against the vanilla 2.6.22.1
> > source:
>
> The reject files all have spaces instead of tabs, so it looks like your
> mailer did some nefarious translation.
>
> Try the attachment ... that usually defeats mailer text translations.
>
> the md5sum just for integrity's sake is 9ba6ace80c06d34b5391407ea68c381a
>
> I tested it against 2.6.22.1 and it applies (but with some offsets):
>
> jejb@hobholes> quilt push
> Applying patch tmp.diff
> patching file drivers/scsi/aic7xxx/aic79xx_osm.c
> Hunk #1 succeeded at 2309 (offset 25 lines).
> Hunk #2 succeeded at 2393 (offset 25 lines).
> Hunk #3 succeeded at 2475 (offset 25 lines).
> Hunk #4 succeeded at 2515 (offset 25 lines).
> Hunk #5 succeeded at 2551 (offset 25 lines).
> Hunk #6 succeeded at 2595 (offset 25 lines).
> Hunk #7 succeeded at 2631 (offset 25 lines).
> Hunk #8 succeeded at 2675 (offset 25 lines).
> patching file drivers/scsi/aic7xxx/aic7xxx_osm.c
> Hunk #1 succeeded at 2356 (offset 39 lines).
> Hunk #2 succeeded at 2425 (offset 39 lines).
>
> James
>
James D. Freels, Ph.D.
Senior Research Staff, HFIR Cold Source, ORNL
http://sunsite.utk.edu/wuot/mt/podcast/051807HIFER.mp3
next prev parent reply other threads:[~2007-07-26 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070725010525.614621080E4@picon.linux-foundation.org>
2007-07-25 2:14 ` [Bug 8366] aic79xx and aic7xxx driver issues James Bottomley
[not found] ` <1185461780.14419.17.camel@fea.ornl.gov>
2007-07-26 15:05 ` James Bottomley
2007-07-26 20:00 ` Freels, James D.
2007-07-26 20:46 ` James Bottomley
2007-07-26 21:13 ` James Bottomley
[not found] ` <1185484597.14419.65.camel@fea.ornl.gov>
2007-07-26 21:29 ` James Bottomley
2007-07-26 21:37 ` Freels, James D.
2007-07-26 21:44 ` James Bottomley
2007-07-26 21:52 ` Freels, James D. [this message]
2007-07-26 21:57 ` Freels, James D.
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=1185486737.14419.73.camel@fea.ornl.gov \
--to=freelsjd@ornl.gov \
--cc=James.Bottomley@SteelEye.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.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