kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Some help about backporting a nic module to 2.6.32 longterm
Date: Mon, 9 Jan 2012 17:30:27 -0800	[thread overview]
Message-ID: <20120110013027.GA11889@kroah.com> (raw)
In-Reply-To: <20120109230818.56662fe0@blade.ferraz.is-a-geek.net>


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

  reply	other threads:[~2012-01-10  1:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 21:19 Some help about backporting a nic module to 2.6.32 longterm André Ferraz
2012-01-09 22:49 ` Greg KH
2012-01-10  1:08   ` André Ferraz
2012-01-10  1:30     ` Greg KH [this message]
2012-01-11 21:42       ` André Ferraz
2012-01-11 22:13         ` Greg KH

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=20120110013027.GA11889@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).