From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Mon, 9 Jan 2012 17:30:27 -0800
Subject: Some help about backporting a nic module to 2.6.32 longterm
In-Reply-To: <20120109230818.56662fe0@blade.ferraz.is-a-geek.net>
References: <20120109191918.7dc7f32f@debo-air.ferraz.is-a-geek.net>
	<20120109224951.GA11339@kroah.com>
	<20120109230818.56662fe0@blade.ferraz.is-a-geek.net>
Message-ID: <20120110013027.GA11889@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Mon, Jan 09, 2012 at 11:08:18PM -0200, Andr? Ferraz wrote:
> Hi Greg,
> 	the problem is that i need to stay with the 2.6.32 grsec
> 	patchset for my servers, if i didn't have any dependencies like
> 	that sure i'll be using the 3.2 kernel.

Why are you using grsec?  Why has it not been updated in the many years
since 2.6.32 was released?

> 	The idea is to just backport this device driver, the rest of
> 	the drivers works pretty well, but i didnt find any HowTo or
> 	some documentation specific to the process of update a driver
> 	on your kernel source.

Just backporting a single driver, usually isn't that easy, as it relies
on other parts of the kernel.

The kernel is ment to be used as a "whole" release, picking and choosing
is very tough at times, and you will be on your own.

I don't recommend it at all.

good luck,

greg k-h