linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-scsi <linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 00/20, v4] Make ib_srp better suited for H.A. purposes
Date: Fri, 23 Nov 2012 16:07:50 +0100	[thread overview]
Message-ID: <50AF9146.5000405@acm.org> (raw)
In-Reply-To: <1348705896.26028.3.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>

On 09/27/12 02:31, David Dillow wrote:
> On Tue, 2012-09-25 at 17:05 +0200, Bart Van Assche wrote:
>> On 08/09/12 17:41, Bart Van Assche wrote:
>>> [ ... ]
>>
>> Hello Dave,
>>
>> More than six weeks have elapsed since I posted version four of this
>> patch series. It would be appreciated if you could tell me when review
>> comments for this patch series will be posted. I'd also like to remind
>> you that some time ago you asked other people to wait with posting more
>> ib_srp patches until this patch series is upstream [1, 2].
>
> Yes, it has taken me far more time than I expected to get to these. I am
> in the middle of fiscal-year-end thrash, and will attend to the SRP
> backlog next week.

(replying to an e-mail of one month ago)

Hello Dave,

Will you have time next week to review the srp-ha patch series ?

Thanks,

Bart.
--
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

  parent reply	other threads:[~2012-11-23 15:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 15:41 [PATCH 00/20, v4] Make ib_srp better suited for H.A. purposes Bart Van Assche
2012-08-09 15:57 ` [PATCH 14/20] srp_transport: Simplify attribute initialization code Bart Van Assche
     [not found] ` <5023DA39.7020000-HInyCGIudOg@public.gmane.org>
2012-08-09 15:56   ` [PATCH 13/20] srp_transport: Fix atttribute registration Bart Van Assche
2012-08-09 15:58   ` [PATCH 15/20] srp_transport: Document sysfs attributes Bart Van Assche
2012-08-09 15:59   ` [PATCH 16/20] ib_srp: Allow SRP disconnect through sysfs Bart Van Assche
2012-08-09 16:02   ` [PATCH 19/20] srp_transport: Add transport layer error handling Bart Van Assche
2012-08-27 18:37   ` [PATCH 00/20, v4] Make ib_srp better suited for H.A. purposes Dongsu Park
2012-08-28 10:04     ` Bart Van Assche
2012-08-28 12:25       ` Dongsu Park
2012-08-28 12:58         ` Bart Van Assche
2012-09-25 15:05   ` Bart Van Assche
2012-09-27  0:31     ` David Dillow
     [not found]       ` <1348705896.26028.3.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2012-11-23 15:07         ` Bart Van Assche [this message]
     [not found]           ` <50AF9146.5000405-HInyCGIudOg@public.gmane.org>
2012-11-26  4:47             ` David Dillow
2012-08-09 16:18 ` Bart Van Assche
     [not found]   ` <5023E2E3.4030602-HInyCGIudOg@public.gmane.org>
2012-08-11  8:29     ` Joseph Glanville

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=50AF9146.5000405@acm.org \
    --to=bvanassche-hinycgiudog@public.gmane.org \
    --cc=dillowda-1Heg1YXhbW8@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-scsi-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;
as well as URLs for NNTP newsgroup(s).