Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: adam radford <aradford@gmail.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, Bo.Yang@lsi.com
Subject: Re: [PATCH 11/11]: megaraid_sas: Documentation/scsi/ChangeLog.megaraid_sas update
Date: Tue, 21 Dec 2010 12:58:52 -0600	[thread overview]
Message-ID: <1292957932.3034.17.camel@mulgrave.site> (raw)
In-Reply-To: <AANLkTikKhNaBpxLiwENzEL+LkFdG+bnbpxv41MhNixb-@mail.gmail.com>

On Tue, 2010-12-14 at 19:11 -0800, adam radford wrote:
> James/Linux-scsi,
> 
> The following patch updates the Documentation/scsi/ChangeLog.megaraid_sas file.

now something in 6-11 doesn't work:

  CC [M]  drivers/scsi/megaraid/megaraid_sas_fusion.o
drivers/scsi/megaraid/megaraid_sas_fusion.c: In function
‘megasas_fusion_ocr_wq’:
drivers/scsi/megaraid/megaraid_sas_fusion.c:2232:10: error: ‘struct
megasas_instance’ has no member named ‘scmd’
drivers/scsi/megaraid/megaraid_sas_fusion.c:2232:35: error: ‘struct
megasas_instance’ has no member named ‘dev’
drivers/scsi/megaraid/megaraid_sas_fusion.c:2233:10: error: ‘struct
megasas_instance’ has no member named ‘dev’
drivers/scsi/megaraid/megaraid_sas_fusion.c:2234:32: error: ‘struct
megasas_instance’ has no member named ‘scmd’
make[1]: *** [drivers/scsi/megaraid/megaraid_sas_fusion.o] Error 1

Just send the redo as a single file ... it looks like the whole patch
series is 125k; that should be just under the reflector limit.

Thanks,

James


--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-12-21 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  3:11 [PATCH 11/11]: megaraid_sas: Documentation/scsi/ChangeLog.megaraid_sas update adam radford
2010-12-21 18:58 ` James Bottomley [this message]
2010-12-21 19:05   ` adam radford
2010-12-21 19:06     ` James Bottomley

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=1292957932.3034.17.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=Bo.Yang@lsi.com \
    --cc=aradford@gmail.com \
    --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