Re: [PATCH RESEND] ntfs: layout.h: delete duplicated words

[Anton Altaparmakov <anton@tuxera.com>]

Hi Randy,

Sorry, I don't know how I missed those originally.

Andrew, please could you add this to your tree for merging with Linus?

Please feel free to add: Acked-by: Anton Altaparmakov <anton@tuxera.com>

Thanks a lot!

Best regards,

	Anton

> On 18 Sep 2020, at 02:20, Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> Drop the repeated words "the" and "in" in comments.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Anton Altaparmakov <anton@tuxera.com>
> Cc: linux-ntfs-dev@lists.sourceforge.net
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
> Adding Andrew to recipients, otherwise this patch is lost/ignored.
> 
> fs/ntfs/layout.h |    4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> --- linux-next-20200917.orig/fs/ntfs/layout.h
> +++ linux-next-20200917/fs/ntfs/layout.h
> @@ -703,7 +703,7 @@ typedef struct {
> /* 14*/	le16 instance;		/* The instance of this attribute record. This
> 				   number is unique within this mft record (see
> 				   MFT_RECORD/next_attribute_instance notes in
> -				   in mft.h for more details). */
> +				   mft.h for more details). */
> /* 16*/	union {
> 		/* Resident attributes. */
> 		struct {
> @@ -1838,7 +1838,7 @@ typedef struct {
>  * Also, each security descriptor is stored twice in the $SDS stream with a
>  * fixed offset of 0x40000 bytes (256kib, the Windows cache manager's max size)
>  * between them; i.e. if a SDS_ENTRY specifies an offset of 0x51d0, then the
> - * the first copy of the security descriptor will be at offset 0x51d0 in the
> + * first copy of the security descriptor will be at offset 0x51d0 in the
>  * $SDS data stream and the second copy will be at offset 0x451d0.
>  */
> typedef struct {


-- 
Anton Altaparmakov <anton at tuxera.com> (replace at with @)
Lead in File System Development, Tuxera Inc., http://www.tuxera.com/
Linux NTFS maintainer