linux-kernel - Re: Backporting newer EDAC drivers to "stable" tree 2.6.27.x?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090817103715.GC3677@aftab>
Date:	Mon, 17 Aug 2009 12:37:15 +0200
From:	Borislav Petkov <borislav.petkov@....com>
To:	Carsten Aulbert <carsten.aulbert@....mpg.de>
CC:	linux-kernel@...r.kernel.org, Doug Thompson <norsk5@...oo.com>
Subject: Re: Backporting newer EDAC drivers to "stable" tree 2.6.27.x?

[ Adding Doug to CC. ]

On Mon, Aug 17, 2009 at 11:06:00AM +0200, Carsten Aulbert wrote:
> what is the recommended way to incorporate newer EDAC drivers from 2.6.30 or 
> later into the long term 2.6.27.x series? Are there ongoing efforts already we 
> could just re-use or does one "just" take the latest patchset and tries to 
> apply it cleanly (enough) to the latest long term kernel?

I've made an AMD64 EDAC backport for RHEL5.4 but since they're using a
heavily patched 2.6.18, this'll be of little or no use for you so you
might just as well slap the driver into .27 sources and fix it up.

There also might be the need to adjust some EDAC core
stuff for which Doug has some patches at the svn repo at
http://bluesmoke.sourceforge.net/ but you'll have to do a bit of
digging yourself :).

-- 
Regards/Gruss,
Boris.

Operating | Advanced Micro Devices GmbH
  System  | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
 Research | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni
  Center  | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
  (OSRC)  | Registergericht München, HRB Nr. 43632

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