From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Mike Heinz <michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Todd Rimmer <todd.rimmer-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Subject: Re: Has the patch for sa busy been accepted?
Date: Wed, 01 Dec 2010 09:43:32 -0500 [thread overview]
Message-ID: <4CF65F14.2030206@dev.mellanox.co.il> (raw)
In-Reply-To: <4C2744E8AD2982428C5BFE523DF8CDCB4A208DF11A-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
Mike,
On 12/1/2010 9:28 AM, Mike Heinz wrote:
> Roland,
>
> Back on November 2nd, Sean said
>
>> Given all this, then I think it would be okay to accept the patch to drop busy responses> from the SA until this framework is in place, which wouldn't be until 2.6.38 or 39.
>>
>> - Sean
>
> I just want to touch base on that - has the SA BUSY patch been accepted for inclusion?
I may have missed this but did my comments on this patch from back on
10/28 get addressed ?
-- 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:[~2010-12-01 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 14:28 Has the patch for sa busy been accepted? Mike Heinz
[not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB4A208DF11A-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-12-01 14:43 ` Hal Rosenstock [this message]
[not found] ` <4CF65F14.2030206-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-12-01 14:45 ` 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=4CF65F14.2030206@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=todd.rimmer-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