Kernel/linux-next
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git synced 2025-01-13 17:28:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

usb: Fixed a few typos

Browse Source 
Fixed typos in comments of various drivers/usb files

Signed-off-by: Mickael Maison <mickael.maison@gmail.com>
Acked-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Mickael Maison 2014-09-18 11:25:04 +02:00 committed by Greg Kroah-Hartman
parent 7adce46784
commit a6cd244b92
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/usb/core/hcd.c
View File

@ -1272,7 +1272,7 @@ EXPORT_SYMBOL_GPL(usb_hcd_unlink_urb_from_ep);
* The usb core itself is however optimized for host controllers that can dma * The usb core itself is however optimized for host controllers that can dma
* using regular system memory - like pci devices doing bus mastering. * using regular system memory - like pci devices doing bus mastering.
* *
* To support host controllers with limited dma capabilites we provide dma * To support host controllers with limited dma capabilities we provide dma
* bounce buffers. This feature can be enabled using the HCD_LOCAL_MEM flag. * bounce buffers. This feature can be enabled using the HCD_LOCAL_MEM flag.
* For this to work properly the host controller code must first use the * For this to work properly the host controller code must first use the
* function dma_declare_coherent_memory() to point out which memory area * function dma_declare_coherent_memory() to point out which memory area

2
drivers/usb/musb/musb_regs.h
View File

@ -577,7 +577,7 @@ static inline u16 musb_read_hwvers(void __iomem *mbase)
{ {
/* /*
* This register is invisible on Blackfin, actually the MUSB * This register is invisible on Blackfin, actually the MUSB
* RTL version of Blackfin is 1.9, so just harcode its value. * RTL version of Blackfin is 1.9, so just hardcode its value.
*/ */
return MUSB_HWVERS_1900; return MUSB_HWVERS_1900;
} }

4
drivers/usb/storage/realtek_cr.c
View File

@ -115,7 +115,7 @@ struct rts51x_chip {
enum RTS51X_STAT state; enum RTS51X_STAT state;
int support_auto_delink; int support_auto_delink;
#endif #endif
/* used to back up the protocal choosen in probe1 phase */ /* used to back up the protocol chosen in probe1 phase */
proto_cmnd proto_handler_backup; proto_cmnd proto_handler_backup;
}; };
@ -925,7 +925,7 @@ static int realtek_cr_autosuspend_setup(struct us_data *us)
(unsigned long)chip); (unsigned long)chip);
fw5895_init(us); fw5895_init(us);
/* enable autosuspend funciton of the usb device */ /* enable autosuspend function of the usb device */
usb_enable_autosuspend(us->pusb_dev); usb_enable_autosuspend(us->pusb_dev);
return 0; return 0;

2
drivers/usb/storage/scsiglue.c
View File

@ -241,7 +241,7 @@ static int slave_configure(struct scsi_device *sdev)
/* Some USB cardreaders have trouble reading an sdcard's last /* Some USB cardreaders have trouble reading an sdcard's last
* sector in a larger then 1 sector read, since the performance * sector in a larger then 1 sector read, since the performance
* impact is negible we set this flag for all USB disks */ * impact is negligible we set this flag for all USB disks */
sdev->last_sector_bug = 1; sdev->last_sector_bug = 1;
/* Enable last-sector hacks for single-target devices using /* Enable last-sector hacks for single-target devices using

2
drivers/usb/storage/usb.c
View File

@ -98,7 +98,7 @@ MODULE_PARM_DESC(quirks, "supplemental list of device IDs and their quirks");
/* The vendor name should be kept at eight characters or less, and /* The vendor name should be kept at eight characters or less, and
* the product name should be kept at 16 characters or less. If a device * the product name should be kept at 16 characters or less. If a device
* has the US_FL_FIX_INQUIRY flag, then the vendor and product names * has the US_FL_FIX_INQUIRY flag, then the vendor and product names
* normally generated by a device thorugh the INQUIRY response will be * normally generated by a device through the INQUIRY response will be
* taken from this list, and this is the reason for the above size * taken from this list, and this is the reason for the above size
* restriction. However, if the flag is not present, then you * restriction. However, if the flag is not present, then you
* are free to use as many characters as you like. * are free to use as many characters as you like.