linux-kernel - Re: SKylake Edac support in linux 2.6.32.696 kernel build

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

Date:   Sun, 2 Sep 2018 17:02:09 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Nitin Gupta <nitin.gupta981@...il.com>
Cc:     ldv-project@...uxtesting.org, devel@...verdev.osuosl.org,
        Pavel Zemlyanoy <zemlyanoy@...ras.ru>,
        linux-kernel@...r.kernel.org, linux-erofs@...ts.ozlabs.org
Subject: Re: SKylake Edac support in linux 2.6.32.696 kernel build

On Sun, Sep 02, 2018 at 03:45:01PM +0530, Nitin Gupta wrote:
> Hi Greg
> 
> i am working on some project which is having huge changes and working
> on kernel-2.6.32-131.696
>  it will be very difficult to back port them into 4.8 .

Why 4.8?  That too is a totally unsupported kernel version.

Anyway, randomly pulling in a driver from a newer by many years, if not
almost a decade old (2.6.32 was released in 2009), is a very difficult
task, and usually almost impossible to go that far back.  That is not
how Linux is developed or meant to be worked with at all.

You are _really_ on your own here, only do this if you _really_ know
what you are doing.  Even then, I would not recommend you do this, as
you are guaranteeing to create a monstrosity that only you can support,
for forever, on your own.

good luck!

greg k-h