Skip to contentSkip to conversation

staging: most: video: remove unnecessary blank line before closing brace

PATCH In review Gerrit Diersmann 2 participants 2 messages Jul 23 – Jul 28

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

PATCH 1/1 staging: most: video: remove unnecessary blank line before closing brace

---
 drivers/staging/most/video/video.c | 1 -
 1 file changed, 1 deletion(-)
drivers/staging/most/video/video.c +0 -1
index 78234620d..5c34f93a0 100644
@@ -439,7 +439,6 @@ static int comp_register_videodev(struct most_video_dev *mdev)
 	mdev->vdev->release = video_device_release;
 
 	return 0;
-
 }
 
 static void comp_unregister_videodev(struct most_video_dev *mdev)
Signature · 1 line
2.55.0
maintainer
#1 lore raw
Quoted 20 lines · Gerrit Diersmann
---
 drivers/staging/most/video/video.c | 1 -
 1 file changed, 1 deletion(-)
drivers/staging/most/video/video.c +0 -1
index 78234620d..5c34f93a0 100644
@@ -439,7 +439,6 @@ static int comp_register_videodev(struct most_video_dev *mdev)
 	mdev->vdev->release = video_device_release;
 
 	return 0;
-
 }
 
 static void comp_unregister_videodev(struct most_video_dev *mdev)
Signature · 1 line
2.55.0

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:

- You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what is needed in order to properly describe the change.

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