linux-kernel - Re: linux-next: Tree for May 27 (infiniband: qib)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 May 2010 15:22:03 -0700
From:	Ralph Campbell <ralph.campbell@...gic.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	Roland Dreier <rdreier@...co.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
Subject: Re: linux-next: Tree for May 27 (infiniband: qib)

On Thu, 2010-05-27 at 15:06 -0700, Randy Dunlap wrote:
> On 05/27/10 14:45, Roland Dreier wrote:
> >  > However, it looks like qib needs to handle DCA config in a way that
> >  > is similar to how it is handled in drivers/net/{myri10ge,igb,ixgbe}/
> >  > instead of assuming that DCA is enabled.
> > 
> > Looks like we're just going to rip out DCA support for now.
> > 
> >  > And please fix the linux-next 2010-may-25 reported qib problem:
> >  >   http://lkml.org/lkml/2010/5/25/321
> > 
> > I think that should be fixed in my for-next branch already (at least I
> > have a patch from Ralph called "IB/qib: Fix undefined symbol error when
> > CONFIG_PCI_MSI=n" in there).
> 
> Sounds good.  Was is posted to linux-rdma?
> 
> thanks,

Yes, I posted it to linux-rdma.

http://www.spinics.net/lists/linux-rdma/msg04140.html

http://www.spinics.net/lists/linux-rdma/msg04187.html


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/