Skip to contentSkip to conversation

drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'

PATCH In review Bogicevic Sasa 3 participants 3 messages Oct 30, 2015 – Oct 31, 2015 Staging

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'

This fixes "Blank lines aren't necessary after an open brace '{'" message from checkpatch.pl

---
 drivers/staging/gdm724x/gdm_mux.c | 1 -
 1 file changed, 1 deletion(-)
drivers/staging/gdm724x/gdm_mux.c +0 -1
index 1cf24e4..0389680 100644
@@ -660,7 +660,6 @@ static struct usb_driver gdm_mux_driver = {
 
 static int __init gdm_usb_mux_init(void)
 {
-
 	mux_rx_wq = create_workqueue("mux_rx_wq");
 	if (mux_rx_wq == NULL) {
 		pr_err("work queue create fail\n");
Signature · 1 line
2.1.4
#1 lore raw
Quoted 5 lines · Bogicevic Sasa

This fixes "Blank lines aren't necessary after an open brace '{'" message from checkpatch.pl

---

You are still using some other tree. This will not apply because of some other change.

regards
sudip

maintainer
#2 lore raw
In reply to Bogicevic Sasa
Quoted 4 lines · Bogicevic Sasa

This fixes "Blank lines aren't necessary after an open brace '{'" message from checkpatch.pl

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.

- You sent multiple patches, yet no indication of which ones should be applied in which order. Greg could just guess, but if you are receiving this email, he guessed wrong and the patches didn't apply. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for a description of how to do this so that Greg has a chance to apply these correctly.

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