From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
James Smart <james.smart@emulex.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: Tree for May 6 (lpfc)
Date: Mon, 06 May 2013 13:36:16 -0400 [thread overview]
Message-ID: <yq1ehdkggdr.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1367858965.1868.24.camel@dabdike> (James Bottomley's message of "Mon, 06 May 2013 09:49:25 -0700")
>>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
>> drivers/built-in.o: In function `lpfc_bg_crc': (.text+0x3cb3c9):
>> undefined reference to `crc_t10dif'
James> That's the usual minor config cockup, isn't it? lpfc apparently
James> also needs the generic checksum, so the fix would seem to be
James> this.
Patch ok as a short term fix.
Longer term I'd like to provide a helper function that HBAs can call to
validate the data and PI scatterlists.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2013-05-06 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 4:42 linux-next: Tree for May 6 Stephen Rothwell
2013-05-06 4:42 ` Stephen Rothwell
2013-05-06 16:14 ` linux-next: Tree for May 6 (lpfc) Randy Dunlap
2013-05-06 16:49 ` James Bottomley
2013-05-06 17:36 ` Martin K. Petersen [this message]
2013-05-06 17:48 ` Randy Dunlap
2013-05-06 17:42 ` linux-next: Tree for May 6 (b43/bcma) Randy Dunlap
2013-05-06 17:42 ` Randy Dunlap
2013-05-07 3:06 ` Larry Finger
2013-05-07 3:06 ` Larry Finger
2013-05-07 3:06 ` Larry Finger
2013-05-07 9:15 ` Johannes Berg
2013-05-07 9:15 ` Johannes Berg
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=yq1ehdkggdr.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=james.smart@emulex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.