From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: danby-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCHv3] libibmad: Add new fields for SM:PortInfoExtended and for PM:PortExtendedSpeedsCounters
Date: Thu, 13 Nov 2014 09:59:13 +0200 [thread overview]
Message-ID: <546464D1.1010402@mellanox.com> (raw)
In-Reply-To: <1415798513-29753-1-git-send-email-danby-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
space please e.g [PATCH v3] and not [PATCHv3]
also as each library as their own git, I see a value in specifying the
library name in the part of the patch subject line which is later
stripped by git am (that is [PATCH libibmad] and not [PATCH] libibmand:)
but not something that remains with this commit forever, since when
observing the code/git, the person that does that knows on which tree
she's looking, right?
--
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:[~2014-11-13 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 13:21 [PATCHv3] libibmad: Add new fields for SM:PortInfoExtended and for PM:PortExtendedSpeedsCounters danby-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb
[not found] ` <1415798513-29753-1-git-send-email-danby-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-11-13 7:52 ` Or Gerlitz
2014-11-13 7:59 ` Or Gerlitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-12 13:10 danby-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb
[not found] ` <1415797832-29112-1-git-send-email-danby-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-11-18 18:45 ` Weiny, Ira
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=546464D1.1010402@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=danby-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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