From: Kumar Gala <kumar.gala@freescale.com>
To: "Greg KH" <greg@kroah.com>
Cc: Deepak Saxena <dsaxena@plexity.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 64-bit resources?
Date: Thu, 5 May 2005 23:12:34 -0500 [thread overview]
Message-ID: <7ade2efc25e965ee53a271cd599ff5ae@freescale.com> (raw)
In-Reply-To: <20050310173522.GA17285@kroah.com>
On Mar 10, 2005, at 11:35 AM, Greg KH wrote:
> On Thu, Mar 10, 2005 at 01:46:10AM -0600, Kumar Gala wrote:
> > Greg,
> >
> > I was wondering what the state of the change to 64-bit resources was?
>
> On hold till I get the time to fix all of the kernel tree up due to the
> changes required.
>
> Unless someone else wants to volunteer to do the work :)
I'll like to see if we can get things into a state to have this ready
for 2.6.13. Do you have a tree around with the changes in it? Do you
have a sense of what work needs to be done. If you give me some
direction on things needing fixing I can start taking a look and
working on patches.
- kumar
next prev parent reply other threads:[~2005-05-06 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 7:46 64-bit resources? Kumar Gala
2005-03-10 17:35 ` Greg KH
2005-03-10 18:09 ` Kumar Gala
2005-03-11 23:58 ` Deepak Saxena
2005-05-06 4:12 ` Kumar Gala [this message]
2005-05-06 4:30 ` 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=7ade2efc25e965ee53a271cd599ff5ae@freescale.com \
--to=kumar.gala@freescale.com \
--cc=dsaxena@plexity.net \
--cc=greg@kroah.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