From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] [TRIVIAL] opensm: Fix small compile error
Date: Tue, 21 Jan 2014 23:33:09 -0500 [thread overview]
Message-ID: <52DF4A05.3060202@dev.mellanox.co.il> (raw)
In-Reply-To: <1390348306.6153.356.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
Hi Al,
On 1/21/2014 6:51 PM, Albert Chu wrote:
> Signed-off-by: Albert L. Chu <chu11-i2BcT+NCU+M@public.gmane.org>
> ---
> osmeventplugin/src/osmeventplugin.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/osmeventplugin/src/osmeventplugin.c b/osmeventplugin/src/osmeventplugin.c
> index 1eaf7ea..0feada8 100644
> --- a/osmeventplugin/src/osmeventplugin.c
> +++ b/osmeventplugin/src/osmeventplugin.c
> @@ -195,7 +195,7 @@ static void report(void *_log, osm_epi_event_id_t event_id, void *event_data)
> fprintf(log->log_file, "Heavy sweep completed\n");
> break;
> case OSM_EVENT_ID_UCAST_ROUTING_DONE:
> - fprintf(log->log_file, "Unicast routing completed %d\n", event_data);
> + fprintf(log->log_file, "Unicast routing completed %p\n", event_data);
I see the problem. I have a different fix for this. Patch shortly.
-- Hal
> break;
> case OSM_EVENT_ID_STATE_CHANGE:
> fprintf(log->log_file, "SM state changed\n");
--
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:[~2014-01-22 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 23:51 [PATCH] [TRIVIAL] opensm: Fix small compile error Albert Chu
[not found] ` <1390348306.6153.356.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2014-01-22 4:33 ` Hal Rosenstock [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=52DF4A05.3060202@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=chu11-i2BcT+NCU+M@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