Re: [PATCH 6/6] advsync: Fix wrong reference to section ``MMIO write barrier''

["Paul E. McKenney" <paulmck@linux.vnet.ibm.com>]

On Sat, Apr 02, 2016 at 09:28:31AM +0900, SeongJae Park wrote:
> A sentence references ``MMIO write barrier'' subsection though the
> section does not exists.  Unfortunately, there is no section for MMIO
> write barrier though appendix ``Why Memory Barriers?'' says about
> mmiowb() subtly.  For the purpose of the sentence, it could be
> alternated with reference to ``Device operations'' subsection because it
> describes about the exceptional case.  For the reason, this commit
> updates it to the reference to ``Device Operations'' subsection.
> 
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Queued, thank you!

							Thanx, Paul

> ---
>  advsync/memorybarriers.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
> index 1fe0953..b511f51 100644
> --- a/advsync/memorybarriers.tex
> +++ b/advsync/memorybarriers.tex
> @@ -1559,7 +1559,7 @@ other strictly in the order specified.
> 
>  The use of LOCK and UNLOCK operations generally precludes the need for
>  other sorts of memory barrier (but note the exceptions mentioned in the
> -subsection ``MMIO write barrier'').
> +Section~\ref{sec:advsync:Device Operations}).
> 
>  \QuickQuiz{}
>  	What effect does the following sequence have on the
> -- 
> 1.9.1
>