[lkml]   [2012]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH 08/23] don't force return value checking in res_counter_charge_nofail
    Since we will succeed with the allocation no matter what, there
    isn't the need to use __must_check with it. It can very well
    be optional.

    Signed-off-by: Glauber Costa <>
    CC: Kamezawa Hiroyuki <>
    CC: Johannes Weiner <>
    CC: Michal Hocko <>
    include/linux/res_counter.h | 2 +-
    1 files changed, 1 insertions(+), 1 deletions(-)

    diff --git a/include/linux/res_counter.h b/include/linux/res_counter.h
    index da81af0..f7621cf 100644
    --- a/include/linux/res_counter.h
    +++ b/include/linux/res_counter.h
    @@ -119,7 +119,7 @@ int __must_check res_counter_charge_locked(struct res_counter *counter,
    unsigned long val);
    int __must_check res_counter_charge(struct res_counter *counter,
    unsigned long val, struct res_counter **limit_fail_at);
    -int __must_check res_counter_charge_nofail(struct res_counter *counter,
    +int res_counter_charge_nofail(struct res_counter *counter,
    unsigned long val, struct res_counter **limit_fail_at);


     \ /
      Last update: 2012-04-21 00:05    [W:3.201 / U:0.108 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site