From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Line Holen <line.holen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v3] Add trap details to notice log message
Date: Fri, 31 May 2013 11:43:35 -0400 [thread overview]
Message-ID: <51A8C527.5070306@dev.mellanox.co.il> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A823736FD2C27A-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 5/31/2013 10:40 AM, Hefty, Sean wrote:
>> Are you suggesting to do this in addition to ib_types.h or instead of ?
>> umad_sm.h seems to hold only a small subset of what's found in ib_types.h.
>
> umad_sm.h was only recently added.
and there is no release yet with those files.
> I'm suggesting to put the definitions there instead of within the opensm header file, so that the definitions are available to applications other than opensm.
My preference would be in addition to rather than instead of. In the
future once there is libibumad release in the field for some time with
these headers, then OpenSM can migrate definitions as makes sense.
-- Hal
--
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 prev parent reply other threads:[~2013-05-31 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 18:16 [PATCH v3] Add trap details to notice log message Line Holen
2013-05-30 18:24 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736FD2C024-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-05-31 8:23 ` Line Holen
[not found] ` <51A85DE4.2000506-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-05-31 14:40 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736FD2C27A-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-05-31 15:43 ` Hal Rosenstock [this message]
[not found] ` <51A8C527.5070306-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-05-31 16:44 ` Line Holen
[not found] ` <51A8D35D.7010203-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-05-31 16:46 ` Hal Rosenstock
2013-06-04 10:42 ` Hal Rosenstock
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=51A8C527.5070306@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=line.holen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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