From: Borislav Petkov <borislav.petkov@amd.com>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Cc: linux-kernel@vger.kernel.org, Doug Thompson <norsk5@yahoo.com>
Subject: Re: Backporting newer EDAC drivers to "stable" tree 2.6.27.x?
Date: Mon, 17 Aug 2009 12:37:15 +0200 [thread overview]
Message-ID: <20090817103715.GC3677@aftab> (raw)
In-Reply-To: <200908171106.00973.carsten.aulbert@aei.mpg.de>
[ 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
prev parent reply other threads:[~2009-08-17 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 9:06 Backporting newer EDAC drivers to "stable" tree 2.6.27.x? Carsten Aulbert
2009-08-17 10:37 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090817103715.GC3677@aftab \
--to=borislav.petkov@amd.com \
--cc=carsten.aulbert@aei.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox