Re: Memory barrier -- fix sample code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2016-08-01 at 21:02 -0700, Paul E. McKenney wrote:
> On Tue, Aug 02, 2016 at 10:32:26AM +1000, Balbir Singh wrote:
>
> > From: Balbir singh <bsingharora@xxxxxxxxx>
> > Date: Tue, 2 Aug 2016 10:26:34 +1000
> > Subject: [PATCH] Correct a sample in memorybarriers.tex
>
> > We probably don't want to show GFP_KERNEL allocation
> > under spin_lock, GFP_ATOMIC seems much better.
>
> > Signed-off-by: Balbir singh <bsingharora@xxxxxxxxx>
> Good catch, applied, thank you!
> 
> However, I had to apply this by hand due to some recent mass changes to
> figures containing code.  Could you please move to current perfbook.git
> for future submissions?
> 
> 							Thanx, Paul

I thought I did a git pull before patching.

My git-head pointed to 413b7bc1cf6d65368300e96016ac15ac728b66fd

I'll double check. Thanks for applying it by hand

Balbir Singh.
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux