From: Eric Sandeen <sandeen@sandeen.net>
To: Donald Douwsma <donaldd@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: PARTIAL TAKE 971050 - Remove linux-2.4 build support
Date: Wed, 26 Sep 2007 20:54:22 -0500 [thread overview]
Message-ID: <46FB0D4E.4070704@sandeen.net> (raw)
In-Reply-To: <46FAFE71.9070000@sgi.com>
Donald Douwsma wrote:
> Christoph Hellwig wrote:
>
>> On Wed, Sep 26, 2007 at 07:25:09AM -0500, Eric Sandeen wrote:
>>
>>> So, what's to be done about xfs_refcache.c... right now it's 2.4-only,
>>> but i'm not convinced that there is similar generic nfs functionality in
>>> 2.6, anyone know for sure?
>>>
>> We keep the inodes around through nfsd, yes. There's a slight problem
>> with ->release beeing called to early, but Greg is working on fixing
>> that using an open files cache in nfsd.
>>
>
> Cool I'll keep that in mind,
>
> I'm going to remove support/Makefile which is 2.4 specific as well.
> Are there any other 2.4 isms you guys know of?
>
> Don
>
>
>
It may be worth diffing the linux-2.4/* and linux-2.6/* to see if there are
any no-ops in 2.6 there only for 2.4... I believe there are.
linux-2.6/mutex.h could probably go away...
hm, there are quite a few 2 or 3 line headers in there, dunno if it makes sense
to have them split out... maybe.
you could lose HAVE_SPLICE and HAVE_FOP_OPEN_EXEC I think
Hmm I wonder if custom do_div is still needed.
-Eric
next prev parent reply other threads:[~2007-09-27 1:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 8:26 PARTIAL TAKE 971050 - Remove linux-2.4 build support donaldd
2007-09-26 12:25 ` Eric Sandeen
2007-09-26 12:28 ` Christoph Hellwig
2007-09-27 0:50 ` Donald Douwsma
2007-09-27 1:54 ` Eric Sandeen [this message]
2007-09-27 2:15 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2007-09-27 3:51 donaldd
2007-09-26 8:34 donaldd
2007-09-29 9:40 ` Christoph Hellwig
2007-09-29 16:27 ` Russell Cattelan
2007-09-26 8:21 donaldd
2007-09-27 2:51 ` Eric Sandeen
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=46FB0D4E.4070704@sandeen.net \
--to=sandeen@sandeen.net \
--cc=donaldd@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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