From: Lethalman <lethalman@fyrebird.net>
To: linux-kernel@vger.kernel.org
Subject: Re: patch to uselib()
Date: Mon, 10 Jan 2005 14:18:47 +0100 [thread overview]
Message-ID: <41E280B7.3080201@fyrebird.net> (raw)
In-Reply-To: <001501c4f699$3c066de0$b0e0a7c8@rootcon4qag3k5>
Breno Silva Pinto wrote:
> Hi Lethalman,
>
> I think i can use the same patch on 2.6.10 kernel , is there any problem ?
>
> Att,
I didn't try 2.6 kernels yet, however it should work fine.
I think you can't use directly the patch because there should be other
changes in the file between 2.4.28 and 2.6.10 ;)
Just modify the file manually, you only need to remove a line and add
the same after the do_brk() call.
--
www.iosn.it * Amministratore Italian Open Source Network
www.fyrebird.net * Fyrebird Hosting Provider - Technical Department
next prev parent reply other threads:[~2005-01-10 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:19 patch to uselib() Breno Silva Pinto
[not found] ` <41E15413.7030509@fyrebird.net>
2005-01-09 16:21 ` Lethalman
[not found] ` <001501c4f699$3c066de0$b0e0a7c8@rootcon4qag3k5>
2005-01-10 13:18 ` Lethalman [this message]
2005-01-09 16:28 ` Henrik Persson
2005-01-10 3:54 ` Mikado
2005-01-10 4:00 ` Mathieu Segaud
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=41E280B7.3080201@fyrebird.net \
--to=lethalman@fyrebird.net \
--cc=linux-kernel@vger.kernel.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).