History

rescounter: remove __must_check from res_counter_charge_nofail()

Since we will succeed with the allocation no matter what, there isn't a need to use __must_check with it. It can very well be optional.

Glauber Costa committed 14 years ago

Commit 04eac7f1 parent 2f3479b1 file · +1 −1Browse files

Showing the changes to include (1 of 1 file). Show all

Unified · Split

include/linux/res_counter.h+1−1
@@ -119,7 +119,7 @@ int __must_check res_counter_charge_locked(struct res_counter *counter, · 118 unmodified lines
119119 unsigned long val, bool force);
120120 int __must_check res_counter_charge(struct res_counter *counter,
121121 unsigned long val, struct res_counter **limit_fail_at);
122−int __must_check res_counter_charge_nofail(struct res_counter *counter,
122+int res_counter_charge_nofail(struct res_counter *counter,
123123 unsigned long val, struct res_counter **limit_fail_at);
124124
125125 /*

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t