From: Mark de Wever <koraq@xs4all.nl>
To: petkovbb@gmail.com,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Gadi Oxman <gadio@netvision.net.il>,
linux-ide@vger.kernel.org, linux-ke
Subject: Re: [patch][repost] ide-tape build fix
Date: Wed, 8 Oct 2008 17:45:52 +0200 [thread overview]
Message-ID: <20081008154552.GA3907@localhost> (raw)
In-Reply-To: <20081008063352.GA13530@gollum.tnic>
On Wed, Oct 08, 2008 at 08:33:52AM +0200, Borislav Petkov wrote:
Hi,
> Bugger, I should be getting at least warnings when compiling this but I don't.
> This is because I don't have CONFIG_LBD enabled. However, the %ld and %d
> format specifiers are also not entirely correct but gcc doesn't warn about them
> - I guess it checks only size but not signedness...
I guess so too.
> Would you like to redo your patch and add a proper comment ontop?
Here you go.
@Boris do you want to add your Signed-off-by too?
@Bart please apply this patch.
--
Subject: ide-tape: Buildfix when IDETAPE_DEBUG_LOG is set to 1.
The format specifier for rq->sector didn't specify the proper size and
signedness. Borislav Petkov discovered that the signedness for
rq->nr_sectors and rq->current_nr_sectors also were incorrect.
Signed-off-by: Mark de Wever <koraq@xs4all.nl>
---
drivers/ide/ide-tape.c | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/ide/ide-tape.c b/drivers/ide/ide-tape.c
index 3833189..3d5f782 100644
--- a/drivers/ide/ide-tape.c
+++ b/drivers/ide/ide-tape.c
@@ -978,9 +978,10 @@ static ide_startstop_t idetape_do_request(ide_drive_t *drive,
struct request *postponed_rq = tape->postponed_rq;
u8 stat;
- debug_log(DBG_SENSE, "sector: %ld, nr_sectors: %ld,"
- " current_nr_sectors: %d\n",
- rq->sector, rq->nr_sectors, rq->current_nr_sectors);
+ debug_log(DBG_SENSE, "sector: %llu, nr_sectors: %lu,"
+ " current_nr_sectors: %u\n",
+ (unsigned long long)rq->sector, rq->nr_sectors,
+ rq->current_nr_sectors);
if (!blk_special_request(rq)) {
/* We do not support buffer cache originated requests. */
--
1.5.6.5
Regards,
Mark de Wever
next prev parent reply other threads:[~2008-10-08 15:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 18:51 [PATCH] IDE-TAPE NULL terminate strings Mark de Wever
2008-09-21 19:24 ` Sergei Shtylyov
2008-09-21 20:08 ` Sergei Shtylyov
2008-09-21 20:29 ` Mark de Wever
2008-09-21 22:12 ` Sergei Shtylyov
2008-09-22 13:16 ` Sergei Shtylyov
2008-09-22 13:56 ` Boris Petkov
2008-09-22 20:41 ` Mark de Wever
2008-09-22 21:08 ` Sergei Shtylyov
2008-09-23 7:48 ` Borislav Petkov
2008-09-23 9:29 ` Sergei Shtylyov
2008-09-23 13:40 ` Boris Petkov
2008-09-23 16:59 ` Mark de Wever
2008-09-23 17:11 ` Boris Petkov
2008-09-23 21:20 ` IDE-TAPE regressions [was: [PATCH] IDE-TAPE NULL terminate strings.] Mark de Wever
2008-10-07 18:26 ` [patch][repost] ide-tape build fix Mark de Wever
2008-10-08 6:33 ` Borislav Petkov
2008-10-08 15:45 ` Mark de Wever [this message]
2008-10-08 16:22 ` Boris Petkov
2008-10-08 18:37 ` Bartlomiej Zolnierkiewicz
2008-09-24 7:10 ` [PATCH] IDE-TAPE NULL terminate strings Borislav Petkov
2008-09-24 9:36 ` Sergei Shtylyov
2008-09-27 17:04 ` Bartlomiej Zolnierkiewicz
2008-09-23 16:14 ` Mark de Wever
2008-09-23 17:10 ` Sergei Shtylyov
2008-09-23 17:27 ` Mark de Wever
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=20081008154552.GA3907@localhost \
--to=koraq@xs4all.nl \
--cc=bzolnier@gmail.com \
--cc=gadio@netvision.net.il \
--cc=linux-ide@vger.kernel.org \
--cc=petkovbb@gmail.com \
--cc=sshtylyov@ru.mvista.com \
/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;
as well as URLs for NNTP newsgroup(s).