From: Hal Rosenstock <hnrose-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] opensm/osm_ucast_ftree.c: Cosmetic commentary changes
Date: Mon, 16 Nov 2009 13:42:22 -0500 [thread overview]
Message-ID: <20091116184222.GA2417@comcast.net> (raw)
Make routine names in comments consistent with actual (changed) names
Signed-off-by: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
diff --git a/opensm/opensm/osm_ucast_ftree.c b/opensm/opensm/osm_ucast_ftree.c
index 1b1da19..76b1d6a 100644
--- a/opensm/opensm/osm_ucast_ftree.c
+++ b/opensm/opensm/osm_ucast_ftree.c
@@ -1975,7 +1975,7 @@ static inline int port_group_compare_load_down(const ftree_port_group_t * p1,
* as it is much faster.
*
* Important note:
- * This function and __osm_ftree_bubble_sort_down must NOT be factorized.
+ * This function and bubble_sort_down must NOT be factorized.
* Although most of the code is the same and a function pointer could be used
* for the compareason function, it would prevent the compareason function to be inlined
* and cost a great deal to performances.
@@ -2047,13 +2047,13 @@ bubble_sort_siblings(ftree_port_group_t ** p_group_array, uint32_t nmemb)
/*
* Function: Sorts an array of port group. Order is decide through
- * __osm_ftree_port_group_compare_load_down ( up counters, least load remote switch, biggest GUID)
+ * port_group_compare_load_down ( up counters, least load remote switch, biggest GUID)
* Given : A port group array and its length. Each port group points to a remote switch (not a HCA)
* As the list is mostly sorted, we used a bubble sort instead of qsort
* as it is much faster.
*
* Important note:
- * This function and __osm_ftree_bubble_sort_up must NOT be factorized.
+ * This function and bubble_sort_up must NOT be factorized.
* Although most of the code is the same and a function pointer could be used
* for the compareason function, it would prevent the compareason function to be inlined
* and cost a great deal to performances.
--
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
next reply other threads:[~2009-11-16 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 18:42 Hal Rosenstock [this message]
[not found] ` <20091116184222.GA2417-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2009-11-26 16:02 ` [PATCH] opensm/osm_ucast_ftree.c: Cosmetic commentary changes Sasha Khapyorsky
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=20091116184222.GA2417@comcast.net \
--to=hnrose-wuw85uim5zdr7s880joybq@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@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