From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
stan.smith-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] opensm/osm_vendor_ibumad: Use OSM_UMAD_MAX_AGENTS rather than UMAD_CA_MAX_AGENTS
Date: Thu, 22 Oct 2009 15:28:46 +0200 [thread overview]
Message-ID: <20091022132846.GI20210@me> (raw)
In-Reply-To: <f0e08f230910220549g1035441dj3b89e543c44efd3a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 08:49 Thu 22 Oct , Hal Rosenstock wrote:
>
> I thought the subject was sufficient and seems to be included in the
> commits. Is that true ?
Subject is just *one* line patch summary and not patch description (as
you trying to use it).
> What are you looking for here that is not
> being done ?
Specifically the patch motivation was unclear to me. And this is due to
violation of patch submitting recommendations: Look at
/usr/src/linux/Documentation/SubmittingPatches
, specifically #2 and #15 in Section 1.
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:[~2009-10-22 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 15:38 [PATCH] opensm/osm_vendor_ibumad: Use OSM_UMAD_MAX_AGENTS rather than UMAD_CA_MAX_AGENTS Hal Rosenstock
[not found] ` <20091019153846.GA22111-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2009-10-22 12:21 ` Sasha Khapyorsky
2009-10-22 12:49 ` Hal Rosenstock
[not found] ` <f0e08f230910220549g1035441dj3b89e543c44efd3a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-22 13:28 ` Sasha Khapyorsky [this message]
2009-10-22 13:35 ` 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=20091022132846.GI20210@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=stan.smith-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