From: Greg KH <greg@kroah.com>
To: Hareesh Nagarajan <hareesh@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Porting kref to a 2.4 kernel (2.4.20 or greater)
Date: Wed, 15 Jun 2005 15:07:34 -0700 [thread overview]
Message-ID: <20050615220734.GC620@kroah.com> (raw)
In-Reply-To: <42B06344.4040909@google.com>
On Wed, Jun 15, 2005 at 10:20:04AM -0700, Hareesh Nagarajan wrote:
> Hi,
>
> What stumbling blocks do you think I would encounter if I wanted to port
> kref to a 2.4.xx kernel? Is kref tightly coupled with the kernel object
> infrastructure found in the 2.6.xx kernel?
Have you looked at the kref code to see if there is any such coupling?
Can you describe any problems you are having doing the uncoupling?
What do you want this in the 2.4 kernel for? You know that no new
features are being accepted for that tree, right?
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-15 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:20 Porting kref to a 2.4 kernel (2.4.20 or greater) Hareesh Nagarajan
2005-06-15 22:07 ` Greg KH [this message]
2005-06-15 22:38 ` Hareesh Nagarajan
2005-06-15 22:47 ` Hareesh Nagarajan
2005-06-16 9:18 ` Dipankar Sarma
2005-06-16 16:45 ` Hareesh Nagarajan
2005-06-16 18:34 ` 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=20050615220734.GC620@kroah.com \
--to=greg@kroah.com \
--cc=hareesh@google.com \
--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