From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0test11pre1ac1
Date: Wed, 08 Nov 2000 18:38:13 -0500 [thread overview]
Message-ID: <3A09E3E5.7A8EB9DB@mandrakesoft.com> (raw)
In-Reply-To: <E13teE4-0000XI-00@the-village.bc.nu>
the network driver changes look ok except for:
epic100:
* CARDBUS is never defined. Should that be CONFIG_CARDBUS?
* just increment the version number. There's no need to add "a" on the
end... this version number just differentiates us from the 'canonical'
Donald Becker version of epic100.c.
net/atm/pvc: return the error value from sock_register, not toss it
away.
ramfs comments:
* Hang on to the ramfs changes for a day or two, there is kmap cleanup
(now returns void*) going to Linus RSN.
* Does ramfs_statfs() need that sb lock in it? Sure free_pages/inodes
might be getting updated on some other CPU, but its statfs so who
cares...
* the default ramfs maxsize, half of all RAM, seems a little
conservative.
* there is no need to kmalloc a private superblock structure, when room
is already allocated inside the superblock structure for private data.
(sb->u)
*
I wonder if we really need removepage added to struct address_space?
That's one API change we shouldn't throw in without discussion, IMHO...
it screams "ramfs-specific hack in core code!"
void __remove_inode_page(struct page *page)
{
+ struct address_space *mapping = page->mapping;
+
+ if (mapping && mapping->a_ops && mapping->a_ops->removepage)
+ mapping->a_ops->removepage(page);
+
And finally, don't you need to EXPORT_SYMBOL pm_devs_lock ?
--
Jeff Garzik |
Building 1024 | Would you like a Twinkie?
MandrakeSoft |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 23:01 Alan Cox
2000-11-08 23:38 ` Jeff Garzik [this message]
2000-11-08 23:58 ` Alan Cox
2000-11-09 3:14 ` VPN Masquerade patch going into 2.2.18final? Dan Browning
2000-11-09 13:09 ` Alan Cox
2000-11-09 0:49 ` Linux 2.4.0test11pre1ac1 David S. Miller
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=3A09E3E5.7A8EB9DB@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®