From: Borislav Petkov <petkovbb@googlemail.com>
To: davem@davemloft.net
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, Mark de Wever <koraq@xs4all.nl>
Subject: [PATCH 1/4] ide-tape: fix debug call
Date: Wed, 15 Jul 2009 17:18:17 +0200 [thread overview]
Message-ID: <1247671100-8173-2-git-send-email-petkovbb@gmail.com> (raw)
In-Reply-To: <1247671100-8173-1-git-send-email-petkovbb@gmail.com>
From: Mark de Wever <koraq@xs4all.nl>
This error only occurs when IDETAPE_DEBUG_LOG is enabled.
Signed-off-by: Mark de Wever <koraq@xs4all.nl>
---
drivers/ide/ide-tape.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/ide/ide-tape.c b/drivers/ide/ide-tape.c
index 013dc59..60d5c41 100644
--- a/drivers/ide/ide-tape.c
+++ b/drivers/ide/ide-tape.c
@@ -583,7 +583,7 @@ static ide_startstop_t idetape_do_request(ide_drive_t *drive,
struct ide_cmd cmd;
u8 stat;
- debug_log(DBG_SENSE, "sector: %llu, nr_sectors: %u\n"
+ debug_log(DBG_SENSE, "sector: %llu, nr_sectors: %u\n",
(unsigned long long)blk_rq_pos(rq), blk_rq_sectors(rq));
BUG_ON(!(blk_special_request(rq) || blk_sense_request(rq)));
--
1.6.3.1
next prev parent reply other threads:[~2009-07-15 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 15:18 [PATCH 0/4] ide-tape: misc stuff Borislav Petkov
2009-07-15 15:18 ` Borislav Petkov [this message]
2009-07-15 15:18 ` [PATCH 2/4] ide-tape: use PFX to all printks Borislav Petkov
2009-07-15 15:18 ` [PATCH 3/4] ide-tape: convert to ide_debug_log macro Borislav Petkov
2009-07-15 15:18 ` [PATCH 4/4] ide-tape: fix handling of postponed rqs Borislav Petkov
2009-07-15 18:16 ` [PATCH 0/4] ide-tape: misc stuff David Miller
2009-07-15 18:43 ` Borislav Petkov
2009-07-15 19:41 ` David Miller
2009-07-16 6:52 ` Borislav Petkov
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=1247671100-8173-2-git-send-email-petkovbb@gmail.com \
--to=petkovbb@googlemail.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=koraq@xs4all.nl \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).