On Tue, Mar 10, 2026 at 12:48:28PM +0100, Philipp Hahn wrote: > Prefer using IS_ERR_OR_NULL() over using IS_ERR() and a manual NULL > check. > > IS_ERR_OR_NULL() already uses likely(!ptr) internally. checkpatch does > not like nesting it: > > WARNING: nested (un)?likely() calls, IS_ERR_OR_NULL already uses > > unlikely() internally > Remove the explicit use of likely(). > > Change generated with coccinelle. > > To: Chris Mason <[email protected]> > To: David Sterba <[email protected]> > Cc: [email protected] > Cc: [email protected] > Signed-off-by: Philipp Hahn <[email protected]>
Added to for-next, we seem to be using IS_ERR_OR_NULL() already in a few other places so this is makes sense for consistency. Thanks.
