public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: John Jolly <jjolly-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org,
	Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ewg] [PATCH] ibdiagpath: Properly index VlArbTable during QoS test
Date: Wed, 06 Oct 2010 17:30:40 +0200	[thread overview]
Message-ID: <4CAC9620.9060609@dev.mellanox.co.il> (raw)
In-Reply-To: <4C8F9617.8010400-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>

On 14-Sep-10 5:34 PM, John Jolly wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Description: ibdiagpath: Properly index VlArbTable during QoS test
> Symptom:     Error 'invalid bareword "vl_entry"' during "QoS on
>               Path Check"
> Problem:     The 'dump' command within the smVlArbTableMad command
>               appends '-vl_entry' to the beginning of the array.
>               The ibdebug.tcl script does not properly handle this
>               extra element at the beginning of the array.
> Solution:    Offset the index value by one when referencing the
>               array.
> Problem-ID:  629166
> - ---

Thanks, applied.

-- YK
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2010-10-06 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C8F9617.8010400@novell.com>
     [not found] ` <4C8F9617.8010400-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2010-10-06 15:30   ` Yevgeny Kliteynik [this message]
     [not found]     ` <4CAC9620.9060609-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-02-07 16:44       ` Patch breaks OFED 1.5.3: [ewg] [PATCH] ibdiagpath: Properly index VlArbTable during QoS test Mike Heinz
     [not found]         ` <4C2744E8AD2982428C5BFE523DF8CDCB4A20B28028-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2011-02-20 14:05           ` Yevgeny Kliteynik
     [not found]             ` <4D611F90.5090701-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-02-21 15:40               ` Mike Heinz
2011-02-21 16:55             ` Mike Heinz
     [not found]               ` <4C2744E8AD2982428C5BFE523DF8CDCB4A20B28AFD-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2011-03-01 21:13                 ` ibdiagpath broken with TCL 8.5 Mike Heinz
     [not found]                   ` <4C2744E8AD2982428C5BFE523DF8CDCB4A20BB3662-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2011-03-03 10:45                     ` Yevgeny Kliteynik
     [not found]                       ` <4D6F7133.4030101-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-03-03 14:22                         ` Mike Heinz
     [not found]                           ` <4C2744E8AD2982428C5BFE523DF8CDCB4A20BB37BE-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2011-03-03 14:48                             ` Yevgeny Kliteynik

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=4CAC9620.9060609@dev.mellanox.co.il \
    --to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=jjolly-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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