Browse Source

doc: fix minor typos in firmware_class README

This is a tiny clean up for typos in the firmware_class README.

Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Kees Cook 11 years ago
parent
commit
b1425189d0
1 changed files with 3 additions and 3 deletions
  1. 3 3
      Documentation/firmware_class/README

+ 3 - 3
Documentation/firmware_class/README

@@ -64,7 +64,7 @@
 
 
 	 if(request_firmware(&fw_entry, $FIRMWARE, device) == 0)
 	 if(request_firmware(&fw_entry, $FIRMWARE, device) == 0)
 	 	copy_fw_to_device(fw_entry->data, fw_entry->size);
 	 	copy_fw_to_device(fw_entry->data, fw_entry->size);
-	 release(fw_entry);
+	 release_firmware(fw_entry);
 
 
  Sample/simple hotplug script:
  Sample/simple hotplug script:
  ============================
  ============================
@@ -74,7 +74,7 @@
 	HOTPLUG_FW_DIR=/usr/lib/hotplug/firmware/
 	HOTPLUG_FW_DIR=/usr/lib/hotplug/firmware/
 
 
 	echo 1 > /sys/$DEVPATH/loading
 	echo 1 > /sys/$DEVPATH/loading
-	cat $HOTPLUG_FW_DIR/$FIRMWARE > /sysfs/$DEVPATH/data
+	cat $HOTPLUG_FW_DIR/$FIRMWARE > /sys/$DEVPATH/data
 	echo 0 > /sys/$DEVPATH/loading
 	echo 0 > /sys/$DEVPATH/loading
 
 
  Random notes:
  Random notes:
@@ -123,6 +123,6 @@
  --------------------
  --------------------
  After firmware cache mechanism is introduced during system sleep,
  After firmware cache mechanism is introduced during system sleep,
  request_firmware can be called safely inside device's suspend and
  request_firmware can be called safely inside device's suspend and
- resume callback, and callers need't cache the firmware by
+ resume callback, and callers needn't cache the firmware by
  themselves any more for dealing with firmware loss during system
  themselves any more for dealing with firmware loss during system
  resume.
  resume.