From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Jack Morgenstein <jackm-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Cc: Yevgeny Kliteynik
<kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Yael Shenhav <yaeli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
Eli Dorfman <Elid-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: mlx4: propagate node_description changes down to FW
Date: Mon, 04 Oct 2010 10:43:46 +0200 [thread overview]
Message-ID: <4CA993C2.1020004@voltaire.com> (raw)
In-Reply-To: <E113D394D7C5DB4F8FF691FA7EE9DB443C180BA9AD-WQlSmcKwN8Te+A/uUDamNg@public.gmane.org>
Jack Morgenstein wrote:
> I have not yet submitted the patch to the list.
sounds like its about time to do that... could you send this to
review/merge into 2.6.37?
From what was commented here and further looking, the sentence "[...]
Upon receiving this trap, OpenSM initiates a heavy sweep, thus updating
the node description properly [...]" isn't accurate, I suggest to change
that into something like "Upon receiving this trap, OpenSM issues
SubnGet(NodeDescription) to the node that sent the trap thus updating
the node description properly" also, I guess "Fixes FM82320" isn't
meaningful for the upstream change log...
Or.
--
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
prev parent reply other threads:[~2010-10-04 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 15:31 mlx4: propagate node_description changes down to FW Or Gerlitz
[not found] ` <4CA8A1BF.4050305-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-10-03 16:01 ` Jack Morgenstein
[not found] ` <E113D394D7C5DB4F8FF691FA7EE9DB443C180BA9AD-WQlSmcKwN8Te+A/uUDamNg@public.gmane.org>
2010-10-03 17:11 ` Hal Rosenstock
2010-10-04 8:43 ` Or Gerlitz [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=4CA993C2.1020004@voltaire.com \
--to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=Elid-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=jackm-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=yaeli-VPRAkNaXOzVS1MOuV/RT9w@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.