From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Borislav Petkov <petkovbb@googlemail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/2] ide-cd: cdrom_decode_status: use return codes instead of naked numbers
Date: Mon, 6 Apr 2009 23:00:15 +0200 [thread overview]
Message-ID: <200904062300.16108.bzolnier@gmail.com> (raw)
In-Reply-To: <1238922962-19727-2-git-send-email-petkovbb@gmail.com>
On Sunday 05 April 2009, Borislav Petkov wrote:
> Remove unused SECTOR_SIZE while at it.
>
> There should be no functional change resulting from this patch.
>
> Signed-off-by: Borislav Petkov <petkovbb@gmail.com>
[...]
> @@ -431,7 +425,7 @@ static int cdrom_decode_status(ide_drive_t *drive, u8 stat)
> /* if we got a CHECK_CONDITION status, queue a request sense command */
> if (stat & ATA_ERR)
> cdrom_queue_request_sense(drive, NULL, NULL);
> - return 1;
> + return REQ_RECOVER;
>
> end_request:
> if (stat & ATA_ERR) {
> @@ -445,9 +439,9 @@ end_request:
> hwif->rq = NULL;
>
> cdrom_queue_request_sense(drive, rq->sense, rq);
> - return 1;
> - } else
> - return 2;
> + return REQ_RECOVER;
> + }
> + return REQ_FAIL;
> }
Could it be that cdrom_newpc_intr() chunk got lost somewhere along the way,
IIRC it was there?
[...]
> +/* internal decode_status codes */
> +#define REQ_CONT 0
> +#define REQ_RECOVER 1
> +#define REQ_FAIL 2
Did you notice my comments about REQ_* in previous mail?
next prev parent reply other threads:[~2009-04-06 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 9:16 [PATCH 2/2] ide-cd: cdrom_decode_status: use return codes instead of naked numbers Borislav Petkov
2009-04-05 9:16 ` Borislav Petkov
2009-04-06 21:00 ` Bartlomiej Zolnierkiewicz [this message]
2009-04-07 6:38 ` 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=200904062300.16108.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@googlemail.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 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.