All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Wilcox, Stephen P, CITPC" <spwilcox@att.com>
Cc: linux-scsi mailing list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH]  DEC hsg80 needs BLIST_REPORTLUN2
Date: Tue, 09 Aug 2005 13:36:12 -0500	[thread overview]
Message-ID: <1123612572.5170.35.camel@mulgrave> (raw)
In-Reply-To: <1123612144.30193.31.camel@aptis101.cqtel.com>

On Tue, 2005-08-09 at 13:29 -0500, Wilcox, Stephen P, CITPC wrote:
> Crap.  I was afraid that my mailer might mangle this...   I created the
> patch with "diff -up" based on the info in "SubmittingPatches" in the
> kernel source tree, but I must admit that I manually edited the patch so
> that It would apply to RedHat's .src.rpms using their canned spec files.
> The working (at least using RedHat's method) patch is attached this time
> rather than pasted in.  If that one still fails to work, the single
> change is all that's really needed.

Well, apparently your ISP mangles attachments:

> The file scsi-blacklist.patch has been replaced, as it is a file type
> that is known for spreading viruses. For assistance, please contact
> your local Desktop Support Personnel or refer to the following website
> for direction. http://antivirus.security.att.com/Default.htm
> 

However I think I have this patch here:

http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=67f4602a392008439ab030ab23181f75e330ba74

If you just verify I got it right.

James



  reply	other threads:[~2005-08-09 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 17:26 [PATCH] DEC hsg80 needs BLIST_REPORTLUN2 Steve Wilcox
2005-08-09 17:51 ` James Bottomley
2005-08-09 18:29   ` Wilcox, Stephen P, CITPC
2005-08-09 18:36     ` James Bottomley [this message]
2005-08-09 18:45       ` Steve Wilcox

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=1123612572.5170.35.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=spwilcox@att.com \
    /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.