From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753172AbbDHI2E (ORCPT ); Wed, 8 Apr 2015 04:28:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42009 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751215AbbDHI2A (ORCPT ); Wed, 8 Apr 2015 04:28:00 -0400 Date: Wed, 8 Apr 2015 10:27:57 +0200 From: "Michael S. Tsirkin" To: linux-kernel@vger.kernel.org Cc: Jonathan Corbet , linux-doc@vger.kernel.org, paulmck@linux.vnet.ibm.com, dhowells@redhat.com Subject: [PATCH] Documentation/memory-barriers.txt: typo fix Message-ID: <1428481589-9151-1-git-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mutt-Fcc: =sent Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fix an obvious typo in the documentation. Signed-off-by: Michael S. Tsirkin --- Documentation/memory-barriers.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index ca2387e..a3a94ff 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt @@ -1711,7 +1711,7 @@ There are some more advanced barrier functions: } The dma_rmb() allows us guarantee the device has released ownership - before we read the data from the descriptor, and he dma_wmb() allows + before we read the data from the descriptor, and the dma_wmb() allows us to guarantee the data is written to the descriptor before the device can see it now has ownership. The wmb() is needed to guarantee that the cache coherent memory writes have completed before attempting a write to -- MST