From: Tomas Henzl <thenzl@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, xjtuwjp@gmail.com,
Vasanthalakshmi.Tharmarajan@pmcs.com,
Suresh.Thiagarajan@pmcs.com, Viswas.G@pmcs.com
Subject: Re: [PATCH 4/4] scsi: pm8001: fix pm8001_store_update_fw
Date: Wed, 30 Jul 2014 15:13:22 +0200 [thread overview]
Message-ID: <53D8EF72.7080208@redhat.com> (raw)
In-Reply-To: <53BE9578.3060902@redhat.com>
On 07/10/2014 03:30 PM, Tomas Henzl wrote:
> On 07/10/2014 08:43 AM, Christoph Hellwig wrote:
>> On Mon, Jul 07, 2014 at 05:20:01PM +0200, Tomas Henzl wrote:
>>> The current implementation may mix the negative value returned
>>> from pm8001_set_nvmd with with count. -(-ENOMEM) could be interpreted
>>> as bytes programmed, this patch fixes it.
>> This still doesn;t look correct to me as err mixes up the driver
>> internal FAIL_* codes with Linux error codes. It seems like for the
>> FAIL_* codes should only go into ->fw_status and the return value
>> should be a proper Linux error code.
> And the fw_status might be later used to show error strings in pm8001_show_update_fw,
> if it is so it depends on the flash utility but it seems likely.
>
>> Funny fact: the FAIL_* / FLASH_IN_PROGRESS codes seems to be the same
>> between aic94xx and pm8001.
> And similar story there too - asd_store_update_bios -...- asd_poll_flash(might return -ENOENT)
>
> Maybe the flash utility ignores the return value or it has never happened.
> ---------------------
>
> I'll try to find what seems to be the most probable way and post it in few days.
Christoph,
from few days it is three weeks and the patch has been just replaced
by "[PATCH 1/3] pm8001: fix pm8001_store_update_fw" sent by Suresh,
so you can drop this patch.
(I've asked Suresh off-list to test it, I didn't want to brick my card by testing
fw flashes.)
Thanks,
Tomas
> This patch is not related to the patches 1-3/4, so just wait with this one.
>
> Thanks, Tomas
>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-07-30 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 15:20 [PATCH 4/4] scsi: pm8001: fix pm8001_store_update_fw Tomas Henzl
2014-07-10 6:43 ` Christoph Hellwig
2014-07-10 13:30 ` Tomas Henzl
2014-07-30 13:13 ` Tomas Henzl [this message]
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=53D8EF72.7080208@redhat.com \
--to=thenzl@redhat.com \
--cc=Suresh.Thiagarajan@pmcs.com \
--cc=Vasanthalakshmi.Tharmarajan@pmcs.com \
--cc=Viswas.G@pmcs.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=xjtuwjp@gmail.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).