linux-kernel - Re: linux-next: manual merge of the driver-core tree with the net tree

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]

Message-Id: <20100520.235008.97331614.davem@davemloft.net>
Date:	Thu, 20 May 2010 23:50:08 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ebiederm@...ssion.com
Cc:	sfr@...b.auug.org.au, greg@...ah.com, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, therbert@...gle.com,
	netdev@...r.kernel.org
Subject: Re: linux-next: manual merge of the driver-core tree with the net
 tree

From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Thu, 20 May 2010 23:46:22 -0700

> It looks right, except perhaps the RPS code looks like it will cause a
> build failure with sysfs disabled, but that has nothing to do with your
> changes.

CONFIG_RPS depends upon CONFIG_SMP && CONFIG_SYSFS, so no that build
failure is not possible.

--
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/