Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1259549 > unrolled thread

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

Started byBogicevic Sasa <brutallesale@gmail.com>
First post2015-10-30 15:40 +0100
Last post2015-11-01 01:00 +0100
Articles 3 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{' Bogicevic Sasa <brutallesale@gmail.com> - 2015-10-30 15:40 +0100
    Re: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary  after an open brace '{' Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2015-10-31 08:50 +0100
    Re: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary  after an open brace '{' Greg KH <gregkh@linuxfoundation.org> - 2015-11-01 01:00 +0100

#1259549 — [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'

FromBogicevic Sasa <brutallesale@gmail.com>
Date2015-10-30 15:40 +0100
Subject[PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'
Message-ID<qpj0t-6Xr-5@gated-at.bofh.it>
This fixes "Blank lines aren't necessary after an open brace '{'"
message from checkpatch.pl

Signed-off-by: Bogicevic Sasa <brutallesale@gmail.com>
---
 drivers/staging/gdm724x/gdm_mux.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/staging/gdm724x/gdm_mux.c b/drivers/staging/gdm724x/gdm_mux.c
index 1cf24e4..0389680 100644
--- a/drivers/staging/gdm724x/gdm_mux.c
+++ b/drivers/staging/gdm724x/gdm_mux.c
@@ -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");
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1259948 — Re: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'

FromSudip Mukherjee <sudipm.mukherjee@gmail.com>
Date2015-10-31 08:50 +0100
SubjectRe: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'
Message-ID<qpz5g-8uB-3@gated-at.bofh.it>
In reply to#1259549
On Fri, Oct 30, 2015 at 03:30:56PM +0100, Bogicevic Sasa wrote:
> This fixes "Blank lines aren't necessary after an open brace '{'"
> message from checkpatch.pl
> 
> Signed-off-by: Bogicevic Sasa <brutallesale@gmail.com>
> ---

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

regards
sudip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1260072 — Re: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'

FromGreg KH <gregkh@linuxfoundation.org>
Date2015-11-01 01:00 +0100
SubjectRe: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'
Message-ID<qpOdY-QP-11@gated-at.bofh.it>
In reply to#1259549
On Fri, Oct 30, 2015 at 03:30:56PM +0100, Bogicevic Sasa wrote:
> This fixes "Blank lines aren't necessary after an open brace '{'"
> message from checkpatch.pl
> 
> Signed-off-by: Bogicevic Sasa <brutallesale@gmail.com>

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web