All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashakvolt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jim Schutt <jaschut-4OHPYypu0djtX7QSmKvirg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Alex Netes <alexne-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH 00/13] opensm: Cleanups and more documentation for torus-2QoS patchset
Date: Sun, 30 Jan 2011 19:12:43 +0200	[thread overview]
Message-ID: <20110130171242.GF25002@me> (raw)
In-Reply-To: <1289599882-15165-1-git-send-email-jaschut-4OHPYypu0djtX7QSmKvirg@public.gmane.org>

Hi Jim,

On 15:11 Fri 12 Nov     , Jim Schutt wrote:
> 
> These patches clean up and add documentation to the
> torus-2QoS routing module for OpenSM.  They apply on
> top of my previous bug-fix patchset from September
> (http://www.spinics.net/lists/linux-rdma/msg05809.html),
> which applies to your torus-2qos branch.

Following your and others feedback. I've merge torus-2qos branch
upstream. Thanks.

Sasha
--
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

  parent reply	other threads:[~2011-01-30 17:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 22:11 [PATCH 00/13] opensm: Cleanups and more documentation for torus-2QoS patchset Jim Schutt
     [not found] ` <1289599882-15165-1-git-send-email-jaschut-4OHPYypu0djtX7QSmKvirg@public.gmane.org>
2010-11-12 22:11   ` [PATCH 01/13] Revert "opensm: Do not require -Q option for torus-2QoS routing engine." Jim Schutt
2010-11-12 22:11   ` [PATCH 02/13] opensm: torus-2QoS requires that QoS be enabled Jim Schutt
2010-11-12 22:11   ` [PATCH 03/13] opensm/osm_ucast_mgr.c: ensure osm_ucast_mgr_process() returns failure when no routing engine runs Jim Schutt
2010-11-12 22:11   ` [PATCH 04/13] opensm: Fill in default QoS values at last possible moment Jim Schutt
2010-11-12 22:11   ` [PATCH 05/13] opensm: Cause torus-2QoS to warn if QoS configuration will cause issues Jim Schutt
2010-11-12 22:11   ` [PATCH 06/13] opensm/osm_torus.c: Also parse DOS line endings in torus-2QoS.conf Jim Schutt
2010-11-12 22:11   ` [PATCH 07/13] opensm/osm_torus.c: Use PRIx64 for GUID printing Jim Schutt
2010-11-12 22:11   ` [PATCH 08/13] opensm/osm_torus.c: Ignore multiple configurations of torus size Jim Schutt
2010-11-12 22:11   ` [PATCH 09/13] opensm/osm_subnet.c: Add torus-2QoS config file option to those configurable via opensm config file Jim Schutt
2010-11-12 22:11   ` [PATCH 10/13] opensm/main.c: Add description of "no_fallback" to "--routing_engine" option documentation Jim Schutt
2010-11-12 22:11   ` [PATCH 11/13] opensm/man/opensm.8.in: Add references to torus-2QoS Jim Schutt
2010-11-12 22:11   ` [PATCH 12/13] opensm: Add torus-2QoS man pages Jim Schutt
2010-11-12 22:11   ` [PATCH 13/13] opensm/doc/current-routing.txt: Sync torus-2QoS information with new " Jim Schutt
2010-11-30 15:23   ` [PATCH 00/13] opensm: Cleanups and more documentation for torus-2QoS patchset Sasha Khapyorsky
2011-01-30 17:12   ` Sasha Khapyorsky [this message]
2011-01-31 15:35     ` Jim Schutt

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=20110130171242.GF25002@me \
    --to=sashakvolt-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alexne-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=jaschut-4OHPYypu0djtX7QSmKvirg@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 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.