On Wed, Aug 10, 2022 at 06:30:00AM -0400, shaomin Deng wrote: > Delete the rebundant word "with" in comments. > > Signed-off-by: shaomin Deng <dengshaomin@xxxxxxxxxx> > --- > drivers/usb/misc/usbtest.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/usb/misc/usbtest.c b/drivers/usb/misc/usbtest.c > index 150090ee4ec1..ac0d75ac2d2f 100644 > --- a/drivers/usb/misc/usbtest.c > +++ b/drivers/usb/misc/usbtest.c > @@ -2638,7 +2638,7 @@ usbtest_do_ioctl(struct usb_interface *intf, struct usbtest_param_32 *param) > * different busses) to use when testing, and allocate one thread per > * test. So discovery is simplified, and we have no device naming issues. > * > - * Don't use these only as stress/load tests. Use them along with with > + * Don't use these only as stress/load tests. Use them along with > * other USB bus activity: plugging, unplugging, mousing, mp3 playback, > * video capture, and so on. Run different tests at different times, in > * different sequences. Nothing here should interact with other devices, > -- > 2.35.1 > Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - Your patch did not apply to any known trees that Greg is in control of. Possibly this is because you made it against Linus's tree, not the linux-next tree, which is where all of the development for the next version of the kernel is at. Please refresh your patch against the linux-next tree, or even better yet, the development tree specified in the MAINTAINERS file for the subsystem you are submitting a patch for, and resend it. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
