* [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c
@ 2026-05-11 6:45 Hanu-man12
0 siblings, 0 replies; 4+ messages in thread
From: Hanu-man12 @ 2026-05-11 6:45 UTC (permalink / raw)
To: gregkh; +Cc: linux-kernel, linux-staging, Hanu-man12
Signed-off-by: Hanu-man12 <shawharshit116@gmail.com>
---
drivers/staging/vme_user/vme_user.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/vme_user/vme_user.c b/drivers/staging/vme_user/vme_user.c
index 11e25c2f6b0a..f5e29933ba68 100644
--- a/drivers/staging/vme_user/vme_user.c
+++ b/drivers/staging/vme_user/vme_user.c
@@ -446,8 +446,9 @@ static void vme_user_vm_close(struct vm_area_struct *vma)
kfree(vma_priv);
}
-static int vme_user_vm_mapped(unsigned long start, unsigned long end, pgoff_t pgoff,
- const struct file *file, void **vm_private_data)
+static int vme_user_vm_mapped(unsigned long start, unsigned long end,
+ pgoff_t pgoff, const struct file *file,
+ void **vm_private_data)
{
const unsigned int minor = iminor(file_inode(file));
struct vme_user_vma_priv *vma_priv;
--
2.53.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c
@ 2026-05-11 8:08 Harshit Shaw
2026-05-11 8:17 ` Greg KH
2026-05-11 8:22 ` Greg KH
0 siblings, 2 replies; 4+ messages in thread
From: Harshit Shaw @ 2026-05-11 8:08 UTC (permalink / raw)
To: gregkh; +Cc: linux-kernel, linux-staging, Harshit Shaw
Wrap the vme_user_vm_mapped() function signature that
exceeded the 80 character line limit as reported by
checkpatch.pl.
No functional change.
Signed-off-by: Harshit Shaw <shawharshit116@gmail.com>
---
drivers/staging/vme_user/vme_user.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/vme_user/vme_user.c b/drivers/staging/vme_user/vme_user.c
index 11e25c2f6b0a..f5e29933ba68 100644
--- a/drivers/staging/vme_user/vme_user.c
+++ b/drivers/staging/vme_user/vme_user.c
@@ -446,8 +446,9 @@ static void vme_user_vm_close(struct vm_area_struct *vma)
kfree(vma_priv);
}
-static int vme_user_vm_mapped(unsigned long start, unsigned long end, pgoff_t pgoff,
- const struct file *file, void **vm_private_data)
+static int vme_user_vm_mapped(unsigned long start, unsigned long end,
+ pgoff_t pgoff, const struct file *file,
+ void **vm_private_data)
{
const unsigned int minor = iminor(file_inode(file));
struct vme_user_vma_priv *vma_priv;
--
2.53.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c
2026-05-11 8:08 [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c Harshit Shaw
@ 2026-05-11 8:17 ` Greg KH
2026-05-11 8:22 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2026-05-11 8:17 UTC (permalink / raw)
To: Harshit Shaw; +Cc: linux-kernel, linux-staging
On Mon, May 11, 2026 at 08:08:15AM +0000, Harshit Shaw wrote:
> Wrap the vme_user_vm_mapped() function signature that
> exceeded the 80 character line limit as reported by
> checkpatch.pl.
You get a full 72 characters here.
> No functional change.
>
> Signed-off-by: Harshit Shaw <shawharshit116@gmail.com>
> ---
> drivers/staging/vme_user/vme_user.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/vme_user/vme_user.c b/drivers/staging/vme_user/vme_user.c
> index 11e25c2f6b0a..f5e29933ba68 100644
> --- a/drivers/staging/vme_user/vme_user.c
> +++ b/drivers/staging/vme_user/vme_user.c
> @@ -446,8 +446,9 @@ static void vme_user_vm_close(struct vm_area_struct *vma)
> kfree(vma_priv);
> }
>
> -static int vme_user_vm_mapped(unsigned long start, unsigned long end, pgoff_t pgoff,
> - const struct file *file, void **vm_private_data)
> +static int vme_user_vm_mapped(unsigned long start, unsigned long end,
> + pgoff_t pgoff, const struct file *file,
> + void **vm_private_data)
100 is an ok line length to stay at, the original code is just fine.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c
2026-05-11 8:08 [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c Harshit Shaw
2026-05-11 8:17 ` Greg KH
@ 2026-05-11 8:22 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2026-05-11 8:22 UTC (permalink / raw)
To: Harshit Shaw; +Cc: linux-kernel, linux-staging
On Mon, May 11, 2026 at 08:08:15AM +0000, Harshit Shaw wrote:
> Wrap the vme_user_vm_mapped() function signature that
> exceeded the 80 character line limit as reported by
> checkpatch.pl.
>
> No functional change.
>
> Signed-off-by: Harshit Shaw <shawharshit116@gmail.com>
> ---
> drivers/staging/vme_user/vme_user.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/vme_user/vme_user.c b/drivers/staging/vme_user/vme_user.c
> index 11e25c2f6b0a..f5e29933ba68 100644
> --- a/drivers/staging/vme_user/vme_user.c
> +++ b/drivers/staging/vme_user/vme_user.c
> @@ -446,8 +446,9 @@ static void vme_user_vm_close(struct vm_area_struct *vma)
> kfree(vma_priv);
> }
>
> -static int vme_user_vm_mapped(unsigned long start, unsigned long end, pgoff_t pgoff,
> - const struct file *file, void **vm_private_data)
> +static int vme_user_vm_mapped(unsigned long start, unsigned long end,
> + pgoff_t pgoff, const struct file *file,
> + void **vm_private_data)
> {
> const unsigned int minor = iminor(file_inode(file));
> struct vme_user_vma_priv *vma_priv;
> --
> 2.53.0
>
>
Didn't my bot ask for these all as a patch series?
{sigh}
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-05-11 8:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-11 8:08 [PATCH] staging: vme_user: fix line exceeding 80 characters in vme_user.c Harshit Shaw
2026-05-11 8:17 ` Greg KH
2026-05-11 8:22 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2026-05-11 6:45 Hanu-man12
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox