linux-kernel - Re: [PATCH] Documentation: xfs: Remove repeated word in comments

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230919221059.GJ348018@frogsfrogsfrogs>
Date:   Tue, 19 Sep 2023 15:10:59 -0700
From:   "Darrick J. Wong" <djwong@...nel.org>
To:     Dave Chinner <dchinner@...hat.com>
Cc:     Charles Han <hanchunchao@...pur.com>, corbet@....net,
        allison.henderson@...cle.com, bhelgaas@...gle.com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-xfs@...r.kernel.org
Subject: Re: [PATCH] Documentation: xfs: Remove repeated word in comments

On Wed, Sep 20, 2023 at 07:03:36AM +1000, Dave Chinner wrote:
> [cc linux-xfs@...r.kernel.org]
> 
> Hi Charles,
> 
> For future reference, can you CC the XFS list on XFS documentation
> changes please?  That's much preferable to sending patches to random
> developers and hoping they notice it....
> 
> On Mon, Sep 18, 2023 at 03:19:05PM +0800, Charles Han wrote:
> > Remove the repeated word "the" in comments.
> > 
> > Signed-off-by: Charles Han <hanchunchao@...pur.com>

Yup.

Reviewed-by: Darrick J. Wong <djwong@...nel.org>

--D

> > ---
> >  Documentation/filesystems/xfs-online-fsck-design.rst | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/filesystems/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs-online-fsck-design.rst
> > index 1625d1131093..a0678101a7d0 100644
> > --- a/Documentation/filesystems/xfs-online-fsck-design.rst
> > +++ b/Documentation/filesystems/xfs-online-fsck-design.rst
> > @@ -1585,7 +1585,7 @@ The transaction sequence looks like this:
> >  2. The second transaction contains a physical update to the free space btrees
> >     of AG 3 to release the former BMBT block and a second physical update to the
> >     free space btrees of AG 7 to release the unmapped file space.
> > -   Observe that the the physical updates are resequenced in the correct order
> > +   Observe that the physical updates are resequenced in the correct order
> 
> Change looks fine, though.
> 
> Reviewed: Dave Chinner <dchinner@...hat.com>
> 
> -- 
> Dave Chinner
> dchinner@...hat.com
>