From: Shane Shrybman <shrybman@sympatico.ca>
To: Paul.Clements@steeleye.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] nbd.c compile warning
Date: 12 Jul 2003 10:50:12 -0400 [thread overview]
Message-ID: <1058021412.10870.13.camel@mars.goatskin.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Here is a patch to fix a compile warning from nbd.c. It has been compile
tested, ( I don't actually use nbd, yet). I have included the patch as
an attachment in case it gets mangled.
--- linux-2.5.75-mm1/drivers/block/nbd.c.orig Sat Jul 12 09:23:45 2003
+++ linux-2.5.75-mm1/drivers/block/nbd.c Sat Jul 12 09:45:06 2003
@@ -261,7 +261,7 @@
dprintk(DBG_TX, "%s: request %p: sending control
(%s@%llu,%luB)\n",
lo->disk->disk_name, req,
nbdcmd_to_ascii(nbd_cmd(req)),
- req->sector << 9, req->nr_sectors << 9);
+ (unsigned long long)req->sector << 9,
req->nr_sectors << 9);
result = sock_xmit(sock, 1, &request, sizeof(request),
(nbd_cmd(req) == NBD_CMD_WRITE)? MSG_MORE: 0);
if (result <= 0) {
Regards,
shane
[-- Attachment #2: nbd.compile.warning.diff --]
[-- Type: text/x-diff, Size: 531 bytes --]
--- linux-2.5.75-mm1/drivers/block/nbd.c.orig Sat Jul 12 09:23:45 2003
+++ linux-2.5.75-mm1/drivers/block/nbd.c Sat Jul 12 09:45:06 2003
@@ -261,7 +261,7 @@
dprintk(DBG_TX, "%s: request %p: sending control (%s@%llu,%luB)\n",
lo->disk->disk_name, req,
nbdcmd_to_ascii(nbd_cmd(req)),
- req->sector << 9, req->nr_sectors << 9);
+ (unsigned long long)req->sector << 9, req->nr_sectors << 9);
result = sock_xmit(sock, 1, &request, sizeof(request),
(nbd_cmd(req) == NBD_CMD_WRITE)? MSG_MORE: 0);
if (result <= 0) {
next reply other threads:[~2003-07-12 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 14:50 Shane Shrybman [this message]
2003-07-13 17:16 ` [PATCH] nbd.c compile warning Paul Clements
-- strict thread matches above, loose matches on Subject: below --
2003-07-12 17:04 Lou Langholtz
2003-07-12 18:35 ` Shane Shrybman
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=1058021412.10870.13.camel@mars.goatskin.org \
--to=shrybman@sympatico.ca \
--cc=Paul.Clements@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
/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