On 2016年07月12日 05:01, David Miller wrote:
The code is correct and optimal as-is. There is no gain to your changes. gfp_any() will do the right thing.In fact, your change makes the code more error prone because if any of these code paths get moved into an atomic context they will break unless somone remembers to also fix up the GFP flags. Meanwhile with the existing use of gfp_any() it will work transparently in such a situation. I'm not applying this.
I see. Thank you for reviewing.
