Searched hist:f818b82b (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/lib/ |
| H A D | test_xarray.c | f818b82b Fri Feb 08 13:02:45 CST 2019 Matthew Wilcox <willy@infradead.org> XArray: Mark xa_insert and xa_reserve as must_check
If the user doesn't care about the return value from xa_insert(), then
they should be using xa_store() instead. The point of xa_reserve() is
to get the return value early before taking another lock, so this should
also be __must_check.
Signed-off-by: Matthew Wilcox <willy@infradead.org>
f818b82b Fri Feb 08 13:02:45 CST 2019 Matthew Wilcox <willy@infradead.org> XArray: Mark xa_insert and xa_reserve as must_check
If the user doesn't care about the return value from xa_insert(), then
they should be using xa_store() instead. The point of xa_reserve() is
to get the return value early before taking another lock, so this should
also be __must_check.
Signed-off-by: Matthew Wilcox <willy@infradead.org>
|
| /openbmc/linux/include/linux/ |
| H A D | xarray.h | f818b82b Fri Feb 08 13:02:45 CST 2019 Matthew Wilcox <willy@infradead.org> XArray: Mark xa_insert and xa_reserve as must_check
If the user doesn't care about the return value from xa_insert(), then
they should be using xa_store() instead. The point of xa_reserve() is
to get the return value early before taking another lock, so this should
also be __must_check.
Signed-off-by: Matthew Wilcox <willy@infradead.org>
f818b82b Fri Feb 08 13:02:45 CST 2019 Matthew Wilcox <willy@infradead.org> XArray: Mark xa_insert and xa_reserve as must_check
If the user doesn't care about the return value from xa_insert(), then
they should be using xa_store() instead. The point of xa_reserve() is
to get the return value early before taking another lock, so this should
also be __must_check.
Signed-off-by: Matthew Wilcox <willy@infradead.org>
|