From: Steven Cole <elenstev@mesatop.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Mark Haverkamp <markh@osdl.org>,
linux-scsi@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5] fix megaraid driver compile error
Date: 06 Feb 2003 14:00:16 -0700 [thread overview]
Message-ID: <1044565217.14310.253.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.44.0302061202430.3545-100000@home.transmeta.com>
On Thu, 2003-02-06 at 13:04, Linus Torvalds wrote:
>
> On 6 Feb 2003, Mark Haverkamp wrote:
> >
> > This moves access of the host element to device since host has been
> > removed from struct scsi_cmnd.
>
> This is whitespace-damaged.
>
> Please fix broken mailers. I generally don't bother to fix up whitespace
> damage from people who can't bother to have a good mailer. It's just not
> worth it - if I try to fix it up (even if it is often trivial), it just
> means that people will continue to send crap patches to me.
>
> Linus
In this case the issue is not a broken mailer, but rather the improper
use of a good one. Mark is using Evolution and so am I. It appears
that he did a cut and paste from an xterm (or something similar) which
converted the tabs to spaces.
For other Evolution users out there, a better way to send patches with
undamaged whitespace and not line-wrapped is to choose Insert and then
Inline Text File. This will send a Linus-compatible inlined (not
attached) patch.
Here is Mark's patch again, sent from Evolution, and not
whitespace-damaged:
Steven
--- linux-2.5.59/drivers/scsi/megaraid.c.orig Thu Feb 6 13:31:24 2003
+++ linux-2.5.59/drivers/scsi/megaraid.c Thu Feb 6 13:33:06 2003
@@ -4515,7 +4515,7 @@
if(scsicmd == NULL) return -ENOMEM;
memset(scsicmd, 0, sizeof(Scsi_Cmnd));
- scsicmd->host = shpnt;
+ scsicmd->device->host = shpnt;
if( outlen || inlen ) {
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,4,0)
@@ -4652,7 +4652,7 @@
if(scsicmd == NULL) return -ENOMEM;
memset(scsicmd, 0, sizeof(Scsi_Cmnd));
- scsicmd->host = shpnt;
+ scsicmd->device->host = shpnt;
if (outlen || inlen) {
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,4,0)
next prev parent reply other threads:[~2003-02-06 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 19:20 Mark Haverkamp
2003-02-06 19:24 ` Christoph Hellwig
2003-02-06 20:04 ` Linus Torvalds
2003-02-06 20:39 ` Mark Haverkamp
2003-02-06 21:00 ` Steven Cole [this message]
2003-02-06 21:02 ` Linus Torvalds
2003-02-06 22:12 ` Steven Cole
2003-02-06 22:26 ` Linus Torvalds
2003-02-06 23:09 ` Steven Cole
2003-02-06 21:16 ` Mark Haverkamp
2003-02-06 23:19 ` David Woodhouse
2003-02-06 23:22 ` Linus Torvalds
2003-02-07 8:45 ` John Bradford
2003-02-07 14:39 ` Alan Cox
2003-02-06 23:40 ` Philippe Gramoullé
2003-02-06 19:59 Matt_Domsch
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=1044565217.14310.253.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@osdl.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®