Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 2 Aug 2022 14:32:15 +0200
From:   David Sterba <dsterba@suse.cz>
To:     Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc:     dsterba@suse.cz, torvalds@linux-foundation.org,
        linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 5.20
Message-ID: <20220802123215.GJ13489@twin.jikos.cz>
Reply-To: dsterba@suse.cz
Mail-Followup-To: dsterba@suse.cz, Qu Wenruo <quwenruo.btrfs@gmx.com>,
        torvalds@linux-foundation.org, linux-btrfs@vger.kernel.org,
        linux-kernel@vger.kernel.org
References: <cover.1659357652.git.dsterba@suse.com>
 <c360943e-c922-9688-5956-e3e5a35c06d8@gmx.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c360943e-c922-9688-5956-e3e5a35c06d8@gmx.com>
User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12)
Precedence: bulk

On Tue, Aug 02, 2022 at 09:11:09AM +0800, Qu Wenruo wrote:
> On 2022/8/2 00:40, David Sterba wrote:
> > Notable fixes:
> >
> > - raid56
> >    - reduce parity writes, skip sectors of stripe when there are no data
> >      updates
> >    - restore reading from stripe cache instead of triggering new read
> 
> Small typo I guess.
> It's the opposite, restore reading from on-disk data instead of using
> stripe cache.

Thanks.

Linus, please replace the sentence with

       - restore reading from on-disk data instead of using stripe
	 cache, this reduces chances to damage correct data due to RMW
	 cycle