From: Brian King <brking@linux.vnet.ibm.com>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Robert C Jennings <rcjenn@us.ibm.com>,
Santiago Leon <sleon@ec.ibm.com>
Subject: Re: [PATCH] Invalid request_limit unnoticed?
Date: Wed, 06 May 2009 16:24:18 -0500 [thread overview]
Message-ID: <4A020002.6020109@linux.vnet.ibm.com> (raw)
In-Reply-To: <49FCA9BE.3030408@gmail.com>
Acked by: Brian King <brking@linux.vnet.ibm.com>
Roel Kluin wrote:
> Remove redundant test on unsigned.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> Maybe a different test is required?
>
> To see that it is unsigned:
>
> git grep -E -n "(req_lim_delta|__be32;$)"
>
> diff --git a/drivers/scsi/ibmvscsi/ibmvscsi.c b/drivers/scsi/ibmvscsi/ibmvscsi.c
> index c9aa761..8d3925f 100644
> --- a/drivers/scsi/ibmvscsi/ibmvscsi.c
> +++ b/drivers/scsi/ibmvscsi/ibmvscsi.c
> @@ -910,9 +910,6 @@ static void login_rsp(struct srp_event_struct *evt_struct)
>
> dev_info(hostdata->dev, "SRP_LOGIN succeeded\n");
>
> - if (evt_struct->xfer_iu->srp.login_rsp.req_lim_delta < 0)
> - dev_err(hostdata->dev, "Invalid request_limit.\n");
> -
> /* Now we know what the real request-limit is.
> * This value is set rather than added to request_limit because
> * request_limit could have been set to -1 by this client.
> --
> 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
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
prev parent reply other threads:[~2009-05-06 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 20:14 [PATCH] Invalid request_limit unnoticed? Roel Kluin
2009-05-06 21:24 ` Brian King [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=4A020002.6020109@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rcjenn@us.ibm.com \
--cc=roel.kluin@gmail.com \
--cc=sleon@ec.ibm.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.