From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
scsi <linux-scsi@vger.kernel.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kxie@chelsio.com
Subject: Re: linux-next: Tree for December 29 (cxgb3i)
Date: Mon, 29 Dec 2008 15:51:07 -0600 [thread overview]
Message-ID: <1230587467.3302.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20081229123517.23fd6169.randy.dunlap@oracle.com>
On Mon, 2008-12-29 at 12:35 -0800, Randy Dunlap wrote:
> On Tue, 30 Dec 2008 03:16:21 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20081219:
> >
> > Undropped tree:
> > scci
> > mtd
> >
> > Dropped trees (temporarily):
> > nfs (akpm request due to 2.6.30 features)
> > kvm (build problem)
> > rr (build poblem)
> > semaphore-removal (due to unfixed conflicts against Linus' tree)
> > cpu_alloc (build problem)
> > audit (difficult conflicts)
> >
> > Linus' tree had three build failures requiring patches and one requiring
> > a revert.
>
>
> linux-next-20081229/drivers/scsi/cxgb3i/cxgb3i_offload.c:499: error: 'struct sk_buff' has no member named 'sp'
> linux-next-20081229/drivers/scsi/cxgb3i/cxgb3i_offload.c:512: error: 'struct sk_buff' has no member named 'sp'
> linux-next-20081229/drivers/scsi/cxgb3i/cxgb3i_offload.c:532: error: 'struct sk_buff' has no member named 'sp'
> linux-next-20081229/drivers/scsi/cxgb3i/cxgb3i_offload.c:533: error: 'struct sk_buff' has no member named 'sp'
In the config 20 questions, my guess for this is CONFIG_XFRM=n
I'm not at all sure why this driver is playing with the secure path ...
I suspect the use needs to be enclosed in #ifdef CONFIG_XFRM pairs, but
I'd like the maintainers to verify.
James
next prev parent reply other threads:[~2008-12-29 21:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 16:16 linux-next: Tree for December 29 Stephen Rothwell
2008-12-29 20:31 ` linux-next: Tree for December 29 (fcoe) Randy Dunlap
2008-12-29 21:35 ` James Bottomley
2008-12-29 21:45 ` James Bottomley
2008-12-29 22:21 ` Randy Dunlap
2008-12-29 20:35 ` linux-next: Tree for December 29 (cxgb3i) Randy Dunlap
2008-12-29 21:51 ` James Bottomley [this message]
2008-12-29 22:10 ` Randy Dunlap
2008-12-29 21:01 ` [PATCH -next] cxgb3i: use same dependencies as CHELSIO_T3 Randy Dunlap
2008-12-29 21:23 ` [PATCH -next v2] cxgb3i: use same dependencies & selects " Randy Dunlap
2008-12-29 21:58 ` James Bottomley
2008-12-29 22:08 ` Randy Dunlap
2008-12-30 16:20 ` James Bottomley
2008-12-30 3:53 ` linux-next: Tree for December 29 (fcoe/libfc) Randy Dunlap
2008-12-30 15:44 ` James Bottomley
2008-12-30 16:54 ` Randy Dunlap
2008-12-30 17:12 ` James Bottomley
2008-12-30 17:36 ` Randy Dunlap
2008-12-30 17:40 ` Kamalesh Babulal
2008-12-30 15:45 ` [BUILD-FAILURE] fcoe driver build fails with !CONFIG_PCI Kamalesh Babulal
-- strict thread matches above, loose matches on Subject: below --
2008-12-30 6:00 linux-next: Tree for December 29 (cxgb3i) Karen Xie
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=1230587467.3302.67.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=kxie@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).