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] staging: vme_user: fix lines exceeding 80 characters in vme_tsi148.c
Date: Sun, 10 May 2026 17:42:15 +0000 [thread overview]
Message-ID: <20260510174215.1444-1-harshit116@gmail.com> (raw)
Signed-off-by: Hanu-man12shaw <harshit116@gmail.com>
---
drivers/staging/vme_user/vme_tsi148.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/vme_user/vme_tsi148.c b/drivers/staging/vme_user/vme_tsi148.c
index 4cf3486646ce..0e8a67fbf562 100644
--- a/drivers/staging/vme_user/vme_tsi148.c
+++ b/drivers/staging/vme_user/vme_tsi148.c
@@ -755,7 +755,8 @@ static int tsi148_alloc_resource(struct vme_master_resource *image,
size, 0x10000, PCIBIOS_MIN_MEM,
0, NULL, NULL);
if (retval) {
- dev_err(tsi148_bridge->parent, "Failed to allocate mem resource for window %d size 0x%lx start 0x%lx\n",
+ dev_err(tsi148_bridge->parent,
+ "Failed to allocate mem resource for window %d size 0x%lx start 0x%lx\n",
image->number, (unsigned long)size,
(unsigned long)image->bus_resource.start);
goto err_resource;
@@ -2252,7 +2253,8 @@ static int tsi148_probe(struct pci_dev *pdev, const struct pci_device_id *id)
struct vme_lm_resource *lm;
if (geoid >= VME_MAX_SLOTS) {
- dev_err(&pdev->dev, "VME geographical address must be between 0 and %d (exclusive), but got %d\n",
+ dev_err(&pdev->dev,
+ "VME geographical address must be between 0 and %d (exclusive), but got %d\n",
VME_MAX_SLOTS, geoid);
return -EINVAL;
}
--
2.53.0
next reply other threads:[~2026-05-10 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 17:42 Hanu-man12shaw [this message]
2026-05-11 7:43 ` [PATCH] staging: vme_user: fix lines exceeding 80 characters in vme_tsi148.c Greg KH
-- strict thread matches above, loose matches on Subject: below --
2026-05-11 8:04 Harshit Shaw
2026-05-11 8:18 ` Greg KH
2026-05-11 6:43 Hanu-man12
2026-05-10 9:04 Hanu-man12shaw
2026-05-10 16:05 ` Greg KH
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=20260510174215.1444-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox