USB: wusbcore: correct spelling mistakes in comments and error string (1076e7a4) · Commits · e / devices / android_kernel_xiaomi_markw

drivers/usb/wusbcore/cbaf.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -184,7 +184,7 @@ static int cbaf_check(struct cbaf *cbaf)
		assoc_request = itr;

		if (top - itr < sizeof(*assoc_request)) {
		dev_err(dev, "Not enough data to decode associaton "
		dev_err(dev, "Not enough data to decode association "
		"request (%zu vs %zu bytes needed)\n",
		top - itr, sizeof(*assoc_request));
		break;

+1 −1

Original line number	Diff line number	Diff line
		@@ -87,7 +87,7 @@ struct aes_ccm_block {
		* B1 contains l(a), the MAC header, the encryption offset and padding.
		*
		* If EO is nonzero, additional blocks are built from payload bytes
		* until EO is exahusted (FIXME: padding to 16 bytes, I guess). The
		* until EO is exhausted (FIXME: padding to 16 bytes, I guess). The
		* padding is not xmitted.
		*/

+2 −2

Original line number	Diff line number	Diff line
		@@ -265,9 +265,9 @@ static void wusbhc_devconnect_acked_work(struct work_struct *work)
		* Addresses: because WUSB hosts have no downstream hubs, we can do a
		* 1:1 mapping between 'port number' and device
		* address. This simplifies many things, as during this
		* initial connect phase the USB stack has no knoledge of
		* initial connect phase the USB stack has no knowledge of
		* the device and hasn't assigned an address yet--we know
		* USB's choose_address() will use the same euristics we
		* USB's choose_address() will use the same heuristics we
		* use here, so we can assume which address will be assigned.
		*
		* USB stack always assigns address 1 to the root hub, so

+1 −1

Original line number	Diff line number	Diff line
		@@ -56,7 +56,7 @@ void wusbhc_sec_destroy(struct wusbhc *wusbhc)
		* @wusb_dev: the device whose PTK the TKID is for
		* (or NULL for a TKID for a GTK)
		*
		* The generated TKID consist of two parts: the device's authenicated
		* The generated TKID consists of two parts: the device's authenticated
		* address (or 0 or a GTK); and an incrementing number. This ensures
		* that TKIDs cannot be shared between devices and by the time the
		* incrementing number wraps around the older TKIDs will no longer be

+5 −5

Original line number	Diff line number	Diff line
		@@ -36,7 +36,7 @@
		*
		* hcd glue with the USB API Host Controller Interface API.
		*
		* nep Notification EndPoint managent: collect notifications
		* nep Notification EndPoint management: collect notifications
		* and queue them with the workqueue daemon.
		*
		* Handle notifications as coming from the NEP. Sends them
		@@ -144,7 +144,7 @@ enum wa_quirks {
		*
		* @wa_descr Can be accessed without locking because it is in
		* the same area where the device descriptors were
		* read, so it is guaranteed to exist umodified while
		* read, so it is guaranteed to exist unmodified while
		* the device exists.
		*
		* Endianess has been converted to CPU's.
		@@ -167,8 +167,8 @@ enum wa_quirks {
		* submitted from an atomic context).
		*
		* FIXME: this needs to be layered up: a wusbhc layer (for sharing
		* comonalities with WHCI), a wa layer (for sharing
		* comonalities with DWA-RC).
		* commonalities with WHCI), a wa layer (for sharing
		* commonalities with DWA-RC).
		*/
		struct wahc {
		struct usb_device *usb_dev;
		@@ -345,7 +345,7 @@ extern void wa_handle_notif_xfer(struct wahc , struct wa_notif_hdr );
		* it...no RC specific function is called...unless I miss
		* something.
		*
		* FIXME: has to go away in favour of an 'struct' hcd based sollution
		* FIXME: has to go away in favour of a 'struct' hcd based solution
		*/
		static inline struct wahc wa_get(struct wahc wa)
		{