From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Mike Heinz <michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org"
<ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org>
Subject: Re: [PATCH] management: adding mad_dump_fields to libibmad
Date: Fri, 7 May 2010 00:02:48 +0300 [thread overview]
Message-ID: <20100506210248.GG7099@me.iol.unh.edu> (raw)
In-Reply-To: <4C2744E8AD2982428C5BFE523DF8CDCB49A4740CD8-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
On 13:27 Thu 06 May , Mike Heinz wrote:
> Sasha asked that I re-submit the patches for perfquery in a slightly different format. This is the first of 3 patches.
I just asked to try to follow the normal patch submission format
described in details there:
http://git.kernel.org/?p=linux/kernel/git/roland/infiniband.git;a=blob;f=Documentation/SubmittingPatches
So each patch will have its own subject line, commit message, etc.
> This patch adds a function to libibmad that allows the caller to dump a configurable range of MAD attributes. Basically, this provides an external interface to the internal function _dump_fields.
>
> Signed Off: Michael Heinz
All three applied. 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
next prev parent reply other threads:[~2010-05-06 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 18:27 [PATCH] management: adding mad_dump_fields to libibmad Mike Heinz
[not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB49A4740CD8-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-06 18:30 ` Mike Heinz
2010-05-06 18:34 ` Mike Heinz
2010-05-06 21:02 ` Sasha Khapyorsky [this message]
[not found] ` <20100506210248.GG7099-o14lFNPAa+WKTadZzrrH2Q@public.gmane.org>
2010-05-06 21:19 ` Mike Heinz
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=20100506210248.GG7099@me.iol.unh.edu \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@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