[PATCH] vme_user: add missing blank line in struct fake_driver

[PATCH] vme_user: add missing blank line in struct fake_driver

[loren coomer]

[-- Attachment #1.1: Type: text/plain, Size: 109 bytes --]

Add a blank line to separate fields in struct fake_driver

Signed-off-by: Loren Coomer <lorencoom@gmail.com>

[-- Attachment #1.2: Type: text/html, Size: 212 bytes --]

[-- Attachment #2: 0001-vme_user-add-missing-blank-line-in-struct-fake_drive.patch --]
[-- Type: text/x-patch, Size: 765 bytes --]

From 69ec78179d88ff83d6ff4c0063f376cde5f091b0 Mon Sep 17 00:00:00 2001
From: lorcoomer <lorencoom@gmail.com>
Date: Sat, 28 Mar 2026 19:36:40 -0700
Subject: [PATCH] vme_user: add missing blank line in struct fake_driver

Signed-off-by Loren Coomer lorencoom@gmail.com
---
 drivers/staging/vme_user/vme_fake.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/vme_user/vme_fake.c b/drivers/staging/vme_user/vme_fake.c
index be4ad47ed526..eb918a8570d5 100644
--- a/drivers/staging/vme_user/vme_fake.c
+++ b/drivers/staging/vme_user/vme_fake.c
@@ -67,6 +67,7 @@ struct fake_driver {
 	unsigned long long lm_base;
 	u32 lm_aspace;
 	u32 lm_cycle;
+
 	void (*lm_callback[4])(void *);
 	void *lm_data[4];
 	struct tasklet_struct int_tasklet;
-- 
2.53.0

Re: [PATCH] vme_user: add missing blank line in struct fake_driver

[Greg KH]

On Sat, Mar 28, 2026 at 07:38:57PM -0700, loren coomer wrote:
> Add a blank line to separate fields in struct fake_driver
> 
> Signed-off-by: Loren Coomer <lorencoom@gmail.com>

> From 69ec78179d88ff83d6ff4c0063f376cde5f091b0 Mon Sep 17 00:00:00 2001
> From: lorcoomer <lorencoom@gmail.com>
> Date: Sat, 28 Mar 2026 19:36:40 -0700
> Subject: [PATCH] vme_user: add missing blank line in struct fake_driver
> 
> Signed-off-by Loren Coomer lorencoom@gmail.com
> ---
>  drivers/staging/vme_user/vme_fake.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/vme_user/vme_fake.c b/drivers/staging/vme_user/vme_fake.c
> index be4ad47ed526..eb918a8570d5 100644
> --- a/drivers/staging/vme_user/vme_fake.c
> +++ b/drivers/staging/vme_user/vme_fake.c
> @@ -67,6 +67,7 @@ struct fake_driver {
>  	unsigned long long lm_base;
>  	u32 lm_aspace;
>  	u32 lm_cycle;
> +
>  	void (*lm_callback[4])(void *);
>  	void *lm_data[4];
>  	struct tasklet_struct int_tasklet;
> -- 
> 2.53.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:

- Your patch was attached, please place it inline so that it can be
  applied directly from the email message itself.

- 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.

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what a proper
  Subject: line should look like.

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

Re: [PATCH] vme_user: add missing blank line in struct fake_driver

[Greg KH]

On Sat, Mar 28, 2026 at 07:38:57PM -0700, loren coomer wrote:
> Add a blank line to separate fields in struct fake_driver
> 
> Signed-off-by: Loren Coomer <lorencoom@gmail.com>

> From 69ec78179d88ff83d6ff4c0063f376cde5f091b0 Mon Sep 17 00:00:00 2001
> From: lorcoomer <lorencoom@gmail.com>
> Date: Sat, 28 Mar 2026 19:36:40 -0700
> Subject: [PATCH] vme_user: add missing blank line in struct fake_driver
> 
> Signed-off-by Loren Coomer lorencoom@gmail.com
> ---
>  drivers/staging/vme_user/vme_fake.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/vme_user/vme_fake.c b/drivers/staging/vme_user/vme_fake.c
> index be4ad47ed526..eb918a8570d5 100644
> --- a/drivers/staging/vme_user/vme_fake.c
> +++ b/drivers/staging/vme_user/vme_fake.c
> @@ -67,6 +67,7 @@ struct fake_driver {
>  	unsigned long long lm_base;
>  	u32 lm_aspace;
>  	u32 lm_cycle;
> +
>  	void (*lm_callback[4])(void *);
>  	void *lm_data[4];
>  	struct tasklet_struct int_tasklet;
> -- 
> 2.53.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:

- Your patch was attached, please place it inline so that it can be
  applied directly from the email message itself.

- 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.

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what a proper
  Subject: line should look like.

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