All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: freelsjd@ornl.gov
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:29:18 -0400	[thread overview]
Message-ID: <1185485358.3501.94.camel@localhost.localdomain> (raw)
In-Reply-To: <1185484597.14419.65.camel@fea.ornl.gov>

On Thu, 2007-07-26 at 17:16 -0400, Freels, James D. wrote:
> James, I would be glad to try the fix.  I can grab the changes below,
> but can you give me the patch command ?  I know how to patch the
> normal kernel sources.  Is this a patch for 2.6.22.1 ?

It was created against current git, but there should be little
difference in the aic driver between that and 2.6.22.1, so it should
apply there as well.

> cd /usr/src/linux-2.6.22.1
> 
> patch -p1 <../your_new_patch
> 
> where your_new_patch is in /usr/src  

Yes, that should do it.

James



  parent reply	other threads:[~2007-07-26 21:29 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 [this message]
2007-07-26 21:37                 ` Freels, James D.
2007-07-26 21:44                   ` James Bottomley
2007-07-26 21:52                     ` Freels, James D.
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=1185485358.3501.94.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=freelsjd@ornl.gov \
    --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 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.