From: Andrew Morton <akpm@zip.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include buffer_head.h in actual users instead of fs.h (6/10)
Date: Thu, 23 May 2002 12:29:51 -0700 [thread overview]
Message-ID: <3CED432F.E0150C06@zip.com.au> (raw)
In-Reply-To: <20020523132700.G24361@infradead.org>
Christoph Hellwig wrote:
>
> Make the 7 file that need it in mm/ include buffer_head.h directly.
> Once again most files shouln't need it and want fixing.
Yup. In fact, some declarations need to be moved out of
buffer_head.h.
> --- 1.91/mm/filemap.c Sun May 19 13:49:50 2002
> +++ edited/mm/filemap.c Thu May 23 13:19:05 2002
> @@ -20,6 +20,16 @@
> #include <linux/iobuf.h>
> #include <linux/hash.h>
> #include <linux/writeback.h>
> +/*
> + * This is needed for the following functions:
> + * - try_to_release_page
This isn't buffer-specific; should be in mm.h or similar.
> + * - block_flushpage
Should never be called - all callers should call
call a_ops->flushpage() (and rename it to
invalidatepage, for heavens sake)
> + * - page_has_buffers
well hopefully we can do something a little tidier than
all the invalidate_foo2() functions. But that's in fact
a happens-to-not-matter bug. Should be using PagePrivate()
in invalidate_this_page2()
> + * - generic_osync_inode
Sigh. Needs to be pushed out to generic_file_write()
callers, I suspect.
etc...
-
prev parent reply other threads:[~2002-05-23 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 12:27 [PATCH] include buffer_head.h in actual users instead of fs.h (6/10) Christoph Hellwig
2002-05-23 19:29 ` Andrew Morton [this message]
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=3CED432F.E0150C06@zip.com.au \
--to=akpm@zip.com.au \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.