Olivier Galibert writes: > Hmmm, then why don't you just drop the return value from the creation > function and BUG() in there is something went wrong. That would allow > for better error messages too. In this instance, BUG would mean that the console text would not ever show up on the screen, and thus the user would never see the message nor get any indication what wrong beyond "it failed to boot". Paul. - 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:
- sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- From: Benjamin Herrenschmidt <[email protected]>
- Re: sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- From: Andrew Morton <[email protected]>
- Re: sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- From: Olivier Galibert <[email protected]>
- Re: sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- From: Andrew Morton <[email protected]>
- Re: sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- From: Olivier Galibert <[email protected]>
- sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- Prev by Date: Re: [PATCH] WorkStruct: Implement generic UP cmpxchg() where an
- Next by Date: Re: 2.6.19: slight performance optimization for lib/string.c's strstrip()
- Previous by thread: Re: sysfs file creation result nightmare
- Next by thread: Re: sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
- Index(es):
 |