From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2.6.36] RDMA/cxgb3: Don't exceed the max HW CQ depth.
Date: Sun, 29 Aug 2010 11:33:37 -0700 [thread overview]
Message-ID: <ada8w3p2rr2.fsf@cisco.com> (raw)
In-Reply-To: <AANLkTim96=HGH_WBaPAUV2zMG0HDgFmixtHE2xQaJMyS-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Bart Van Assche's message of "Sun, 29 Aug 2010 09:16:44 +0200")
> The easiest way is to add "CC: <stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>" when submitting a
> patch. An alternative is after the patch has been accepted in Linus'
> tree to submit it to stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org with a reference to the commit
> ID in Linus' tree. More information can be found in
> Documentation/stable_kernel_rules.txt.
Yep, this is exactly right. In this case I'll add the cc to the commit
message so you don't need to do anything more.
- R.
--
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-08-29 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 13:35 [PATCH 2.6.36] RDMA/cxgb3: Don't exceed the max HW CQ depth Steve Wise
[not found] ` <20100828133505.14439.81049.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-08-28 13:40 ` Steve Wise
[not found] ` <4C7911B4.9070904-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-08-29 7:16 ` Bart Van Assche
[not found] ` <AANLkTim96=HGH_WBaPAUV2zMG0HDgFmixtHE2xQaJMyS-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-29 18:33 ` Roland Dreier [this message]
2010-09-02 21:52 ` Roland Dreier
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=ada8w3p2rr2.fsf@cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.