From: Hanu-man12shaw <shawharshit116@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
Hanu-man12shaw <harshit116@gmail.com>
Subject: [PATCH 2/2] staging: vme_user: fix line exceeding 80 characters in vme_user.c
Date: Sun, 10 May 2026 18:33:55 +0000 [thread overview]
Message-ID: <20260510183355.2345-1-harshit116@gmail.com> (raw)
Signed-off-by: Hanu-man12shaw <harshit116@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
reply other threads:[~2026-05-10 18:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260510183355.2345-1-harshit116@gmail.com \
--to=shawharshit116@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harshit116@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.