From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
Subject: SKylake Edac support in linux 2.6.32.696 kernel build
Date: Sun, 2 Sep 2018 17:02:09 +0200 [thread overview]
Message-ID: <20180902150209.GA25883@kroah.com> (raw)
In-Reply-To: <CAB3_1Nv2P7uh6ypy4RXQXejeJ9PpF2KWdFK3V5OPHq_+4rANAw@mail.gmail.com>
On Sun, Sep 02, 2018@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
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nitin Gupta <nitin.gupta981@gmail.com>
Cc: ldv-project@linuxtesting.org, devel@driverdev.osuosl.org,
Pavel Zemlyanoy <zemlyanoy@ispras.ru>,
linux-kernel@vger.kernel.org, linux-erofs@lists.ozlabs.org
Subject: Re: SKylake Edac support in linux 2.6.32.696 kernel build
Date: Sun, 2 Sep 2018 17:02:09 +0200 [thread overview]
Message-ID: <20180902150209.GA25883@kroah.com> (raw)
In-Reply-To: <CAB3_1Nv2P7uh6ypy4RXQXejeJ9PpF2KWdFK3V5OPHq_+4rANAw@mail.gmail.com>
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
next prev parent reply other threads:[~2018-09-02 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 11:16 SKylake Edac support in linux 2.6.32.696 kernel build Nitin Gupta
2018-08-31 11:23 ` Nitin Gupta
2018-08-31 16:14 ` Greg Kroah-Hartman
2018-08-31 16:14 ` Greg Kroah-Hartman
2018-08-31 17:52 ` Nitin Gupta
2018-08-31 19:47 ` Greg Kroah-Hartman
2018-08-31 19:47 ` Greg Kroah-Hartman
2018-09-02 10:15 ` Nitin Gupta
2018-09-02 15:02 ` Greg Kroah-Hartman [this message]
2018-09-02 15:02 ` Greg Kroah-Hartman
2018-09-02 17:17 ` Nitin Gupta
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=20180902150209.GA25883@kroah.com \
--to=gregkh@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.