From: Randy Dunlap <randy.dunlap@oracle.com>
To: Bernd Schubert <bs@q-leap.de>
Cc: linux-kernel@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
brian@clusterfs.com
Subject: Re: patch: improve generic_file_buffered_write()
Date: Wed, 5 Sep 2007 08:35:29 -0700 [thread overview]
Message-ID: <20070905083529.a1c8a0a9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200709051546.06224.bs@q-leap.de>
On Wed, 5 Sep 2007 15:45:36 +0200 Bernd Schubert wrote:
> Hi,
meta-comments:
> filemap.c | 144
> +++++++++++++++++++++++++++++++++++++++++---------------------
> 1 file changed, 96 insertions(+), 48 deletions(-)
Use "diffstat -p 1 -w 70" per Documentation/SubmittingPatches.
> Index: linux-2.6.20.3/mm/filemap.c
> ===================================================================
> --- linux-2.6.20.3.orig/mm/filemap.c 2007-09-04 13:43:04.000000000 +0200
> +++ linux-2.6.20.3/mm/filemap.c 2007-09-05 12:39:23.000000000 +0200
> @@ -2057,6 +2057,19 @@
> }
> EXPORT_SYMBOL(generic_file_direct_write);
>
> +/**
> + * This function will do 3 main tasks for each iov:
> + * - prepare a write
> + * - copy the data from iov into a new page
> + * - commit this page
> + * @iob: file operations
> + * @iov: vector of data to write
> + * @nr_segs: number of iov segments
> + * @pos: position in the file
> + * @ppos: position in the file after this function
> + * @count: number of bytes to write
> + * written: offset in iov->base (data to skip on write)
> + */
> ssize_t
> generic_file_buffered_write(struct kiocb *iocb, const struct iovec *iov,
> unsigned long nr_segs, loff_t pos, loff_t *ppos,
Use proper kernel-doc notation, per Documentation/kernel-doc-nano-HOWTO.txt.
This comment block should be:
/**
* generic_file_buffered_write - handle an iov
* @iocb: file operations
* @iov: vector of data to write
* @nr_segs: number of iov segments
* @pos: position in the file
* @ppos: position in the file after this function
* @count: number of bytes to write
* @written: offset in iov->base (data to skip on write)
*
* This function will do 3 main tasks for each iov:
* - prepare a write
* - copy the data from iov into a new page
* - commit this page
*/
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-09-05 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 13:45 patch: improve generic_file_buffered_write() Bernd Schubert
2007-09-05 15:35 ` Randy Dunlap [this message]
2007-09-05 17:41 ` patch: improve generic_file_buffered_write() (2nd try 1/2) Bernd Schubert
2007-09-05 17:49 ` patch: improve generic_file_buffered_write() (2nd try 2/2) Bernd Schubert
2007-09-08 4:15 ` patch: improve generic_file_buffered_write() (2nd try 1/2) Nick Piggin
2007-09-07 20:01 ` Goswin von Brederlow
2007-09-08 6:28 ` Nick Piggin
2007-09-07 21:12 ` Goswin von Brederlow
2007-09-08 7:25 ` Nick Piggin
2007-09-08 7:31 ` Nick Piggin
2007-09-08 9:43 ` Goswin von Brederlow
2007-09-07 20:12 ` Nick Piggin
2007-09-07 21:00 ` Goswin von Brederlow
2007-09-08 7:14 ` Nick Piggin
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=20070905083529.a1c8a0a9.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=bfields@fieldses.org \
--cc=brian@clusterfs.com \
--cc=bs@q-leap.de \
--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