Skip to contentSkip to conversation

drivers: usb: musb: musb_gadget: replaced bare unsigned to unsigned int

PATCH In review Neel Chakraborty 2 participants 2 messages Jun 6, 2023

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 2/2 drivers: usb: musb: musb_gadget: replaced bare unsigned to unsigned int

Replaced code that was using bare unsigned to use unsigned int

---
 drivers/usb/musb/musb_gadget.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/musb/musb_gadget.c +1 -1
index 3cb7fc4c84ed..8912118883dc 100644
@@ -521,7 +521,7 @@ static void rxstate(struct musb *musb, struct musb_request *req)
 	struct usb_request	*request = &req->request;
 	struct musb_ep		*musb_ep;
 	void __iomem		*epio = musb->endpoints[epnum].regs;
-	unsigned		len = 0;
+	unsigned int		len = 0;
 	u16			fifo_count;
 	u16			csr = musb_readw(epio, MUSB_RXCSR);
 	struct musb_hw_ep	*hw_ep = &musb->endpoints[epnum];
Signature · 1 line
2.40.1
maintainer
#1 lore raw
Quoted 6 lines · Neel Chakraborty

Replaced code that was using bare unsigned to use unsigned int

---
 drivers/usb/musb/musb_gadget.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Where is patch 1/2 of this series?

As it looks like you are new to kernel development, I strongly recomomend you start out doing coding cleanups in the drivers/staging/ portion of the kernel first, as that is explicitly what it is there for. That keeps kernel developers and maintainers of other subsystems from having to work through basic issues like this.

Also, I recommend re-reading the kernel documentation for how to submit a patch, this isn't the correct way :)

thanks,

greg k-h