lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <09a4135a-de15-2c1d-5356-c55c77d6f3c0@oracle.com>
Date:   Wed, 14 Oct 2020 07:57:15 -0500
From:   Dave Kleikamp <dave.kleikamp@...cle.com>
To:     Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org
Cc:     jfs-discussion@...ts.sourceforge.net
Subject: Re: [PATCH] jfs: delete duplicated words in header files

Sorry. I've neglected JFS lately. I'll review and merge these today or
tomorrow, along with some others in my queue.

Shaggy

On 10/14/20 12:29 AM, Randy Dunlap wrote:
> ping.
> 
> On 7/19/20 5:13 PM, Randy Dunlap wrote:
>> Drop the repeated words "allocation" and "if" in comments.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
>> Cc: Dave Kleikamp <shaggy@...nel.org>
>> Cc: jfs-discussion@...ts.sourceforge.net
>> ---
>>  fs/jfs/jfs_extent.h |    2 +-
>>  fs/jfs/jfs_logmgr.h |    2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> --- linux-next-20200717.orig/fs/jfs/jfs_extent.h
>> +++ linux-next-20200717/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-20200717.orig/fs/jfs/jfs_logmgr.h
>> +++ linux-next-20200717/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
>>
> 
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ