[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <C66390C8-E5E5-4EF5-AF25-1BC7C0BFC114@zytor.com>
Date: Wed, 20 Jan 2016 15:24:19 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Michael Brown <mcb30@...e.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>
CC: 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
On January 20, 2016 3:15:48 PM PST, Michael Brown <mcb30@...e.org> wrote:
>>> + * 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
Yes, that request has already been made :)
--
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.
Powered by blists - more mailing lists