[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <56A01524.5080508@ipxe.org>
Date: Wed, 20 Jan 2016 23:15:48 +0000
From: Michael Brown <mcb30@...e.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>
CC: hpa@...or.com, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
rusty@...tcorp.com.au, luto@...capital.net,
boris.ostrovsky@...cle.com, jgross@...e.com, JBeulich@...e.com,
joro@...tes.org, ryabinin.a.a@...il.com, andreyknvl@...gle.com,
long.wanglong@...wei.com, qiuxishi@...wei.com,
aryabinin@...tuozzo.com, mchehab@....samsung.com,
valentinrothberg@...il.com, peter.senna@...il.com, mcgrof@...e.com,
x86@...nel.org, xen-devel@...ts.xensource.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC v1 2/8] tables.h: add linker table support
>> + * To solve this problem linker tables can be used on Linux, it enables you to
>> + * always force compiling of select features that one wishes to avoid bit-rot
>> + * while still enabling you to disable linking feature code into the final
>> + * kernel image or building certain modules if the features have been disabled
>> + * via Kconfig. The code is derivative of gPXE linker table's solution.
I missed the start of this thread. However, asking as the author of the
original Etherboot/gPXE/iPXE linker table solution: please change all
references from "gPXE" to "iPXE".
Thanks,
Michael
Powered by blists - more mailing lists