linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-fsdevel@vger.kernel.org
Cc: Dave Kleikamp <shaggy@kernel.org>, jfs-discussion@lists.sourceforge.net
Subject: Re: [PATCH] jfs: delete duplicated words + other fixes
Date: Tue, 13 Oct 2020 22:30:06 -0700	[thread overview]
Message-ID: <8a632de9-d4ef-3f90-036a-7f9cc35eb8a9@infradead.org> (raw)
In-Reply-To: <20200805024901.12181-1-rdunlap@infradead.org>

ping.

On 8/4/20 7:49 PM, Randy Dunlap wrote:
> Delete repeated words in fs/jfs/.
> {for, allocation, if, the}
> Insert "is" in one place to correct the grammar.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> To: linux-fsdevel@vger.kernel.org
> Cc: Dave Kleikamp <shaggy@kernel.org>
> Cc: jfs-discussion@lists.sourceforge.net
> ---
>  fs/jfs/jfs_dmap.c   |    2 +-
>  fs/jfs/jfs_extent.c |    2 +-
>  fs/jfs/jfs_extent.h |    2 +-
>  fs/jfs/jfs_logmgr.h |    2 +-
>  fs/jfs/jfs_txnmgr.c |    2 +-
>  fs/jfs/jfs_xtree.c  |    2 +-
>  6 files changed, 6 insertions(+), 6 deletions(-)
> 
> --- linux-next-20200804.orig/fs/jfs/jfs_dmap.c
> +++ linux-next-20200804/fs/jfs/jfs_dmap.c
> @@ -668,7 +668,7 @@ unlock:
>   *		this does not succeed, we finally try to allocate anywhere
>   *		within the aggregate.
>   *
> - *		we also try to allocate anywhere within the aggregate for
> + *		we also try to allocate anywhere within the aggregate
>   *		for allocation requests larger than the allocation group
>   *		size or requests that specify no hint value.
>   *
> --- linux-next-20200804.orig/fs/jfs/jfs_extent.c
> +++ linux-next-20200804/fs/jfs/jfs_extent.c
> @@ -575,7 +575,7 @@ extBalloc(struct inode *ip, s64 hint, s6
>   *	blkno	 - starting block number of the extents current allocation.
>   *	nblks	 - number of blocks within the extents current allocation.
>   *	newnblks - pointer to a s64 value.  on entry, this value is the
> - *		   the new desired extent size (number of blocks).  on
> + *		   new desired extent size (number of blocks).  on
>   *		   successful exit, this value is set to the extent's actual
>   *		   new size (new number of blocks).
>   *	newblkno - the starting block number of the extents new allocation.
> --- linux-next-20200804.orig/fs/jfs/jfs_extent.h
> +++ linux-next-20200804/fs/jfs/jfs_extent.h
> @@ -5,7 +5,7 @@
>  #ifndef	_H_JFS_EXTENT
>  #define _H_JFS_EXTENT
>  
> -/*  get block allocation allocation hint as location of disk inode */
> +/*  get block allocation hint as location of disk inode */
>  #define	INOHINT(ip)	\
>  	(addressPXD(&(JFS_IP(ip)->ixpxd)) + lengthPXD(&(JFS_IP(ip)->ixpxd)) - 1)
>  
> --- linux-next-20200804.orig/fs/jfs/jfs_logmgr.h
> +++ linux-next-20200804/fs/jfs/jfs_logmgr.h
> @@ -132,7 +132,7 @@ struct logpage {
>   * (this comment should be rewritten !)
>   * jfs uses only "after" log records (only a single writer is allowed
>   * in a page, pages are written to temporary paging space if
> - * if they must be written to disk before commit, and i/o is
> + * they must be written to disk before commit, and i/o is
>   * scheduled for modified pages to their home location after
>   * the log records containing the after values and the commit
>   * record is written to the log on disk, undo discards the copy
> --- linux-next-20200804.orig/fs/jfs/jfs_txnmgr.c
> +++ linux-next-20200804/fs/jfs/jfs_txnmgr.c
> @@ -1474,7 +1474,7 @@ static int diLog(struct jfs_log * log, s
>  		 * For the LOG_NOREDOINOEXT record, we need
>  		 * to pass the IAG number and inode extent
>  		 * index (within that IAG) from which the
> -		 * the extent being released.  These have been
> +		 * extent is being released.  These have been
>  		 * passed to us in the iplist[1] and iplist[2].
>  		 */
>  		lrd->log.noredoinoext.iagnum =
> --- linux-next-20200804.orig/fs/jfs/jfs_xtree.c
> +++ linux-next-20200804/fs/jfs/jfs_xtree.c
> @@ -3684,7 +3684,7 @@ s64 xtTruncate(tid_t tid, struct inode *
>   *
>   * function:
>   *	Perform truncate to zero length for deleted file, leaving the
> - *	the xtree and working map untouched.  This allows the file to
> + *	xtree and working map untouched.  This allows the file to
>   *	be accessed via open file handles, while the delete of the file
>   *	is committed to disk.
>   *
> 


-- 
~Randy


      reply	other threads:[~2020-10-14  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05  2:49 [PATCH] jfs: delete duplicated words + other fixes Randy Dunlap
2020-10-14  5:30 ` Randy Dunlap [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=8a632de9-d4ef-3f90-036a-7f9cc35eb8a9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=shaggy@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;
as well as URLs for NNTP newsgroup(s).