linux-kernel - RE: linux-next: build warnings after merge of the final tree (mtd tree related)

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] [day] [month] [year] [list]

Date:	Tue, 26 Oct 2010 17:48:34 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	H Hartley Sweeten <hartleys@...ionengravers.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: linux-next: build warnings after merge of the final tree (mtd
 tree related)

On Tue, 2010-10-26 at 11:43 -0500, H Hartley Sweeten wrote:
> I didn't follow the logic for the MTD_MAP_BANK_WIDTH_* all the way thru.
> 
> Honestly I still don't quite get it.  If MTD_CFI_GEOMETRY is n wouldn't
> all the MTD_MAP_BANK_WIDTH_* also be n? 

config MTD_CFI_GEOMETRY
        bool "Specific CFI Flash geometry selection"
        depends on MTD_CFI_ADV_OPTIONS
        help
          This option does not affect the code directly, but will enable
          some other configuration options which would allow you to reduce
          the size of the kernel by including support for only certain
          arrangements of CFI chips. If unsure, say 'N' and all options
          which are supported by the current code will be enabled.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation

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