From: Hugh Dickins <hugh@veritas.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: akpm@osdl.org, lkml <linux-kernel@vger.kernel.org>, hch@lst.de
Subject: Re: [PATCH] generic_file_write_nolock cleanup
Date: Mon, 30 Jan 2006 17:20:28 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0601301717060.5478@goblin.wat.veritas.com> (raw)
In-Reply-To: <1138640165.28382.3.camel@dyn9047017102.beaverton.ibm.com>
On Mon, 30 Jan 2006, Badari Pulavarty wrote:
>
> generic_file_write_nolock() and __generic_file_write_nolock() seems
> to be doing exactly same thing. Why do we have 2 of these ?
> Can we kill __generic_file_write_nolock() ?
Doesn't generic_file_write_nolock() call generic_file_aio_write_nolock(),
but __generic_file_write_nolock() call __generic_file_aio_write_nolock()?
With the first doing some syncing which the __second doesn't do?
Lovely names in mm/filemap.c, aren't they?
Hugh
next prev parent reply other threads:[~2006-01-30 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 16:56 Badari Pulavarty
2006-01-30 17:20 ` Hugh Dickins [this message]
2006-01-30 18:07 ` Badari Pulavarty
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=Pine.LNX.4.61.0601301717060.5478@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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
all inboxes | Powered by JetHome®