Re: __must_check (stir the pot :-))

Stephen Rothwell wrote:

where sysfs_create_file() is marked __must_check and sysdev_create_file()
isn't.

So the questions come to mind:  Do we really care if our core
infrastructure doesn't?  Can we care if the core infrastructure doesn't
propogate the error returns?



Yes, we should propagate the markers as needed...

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- __must_check (stir the pot :-))
  - From: Stephen Rothwell <[email protected]>

Prev by Date: Re: __must_check (stir the pot :-))
Next by Date: [PATCH] Documentation: Fix the explanation of Kconfig files.
Previous by thread: Re: __must_check (stir the pot :-))
Next by thread: Bug : support for Texas Instrument Card Reader 4 in 1 - Failed to allocate ressources
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]