From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Vasiliy Tolstov <v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: linux 3.8.6 and srp backports
Date: Mon, 08 Apr 2013 10:23:48 +0200 [thread overview]
Message-ID: <51627E94.9010104@acm.org> (raw)
In-Reply-To: <CACaajQu0OHOz0Ok-SkxHWPpTBEfRjNFGrPF8z5HX0bdq+sgXeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 04/08/13 10:00, Vasiliy Tolstov wrote:
> Hello. Some times ago, when i'm use kernel 3.6 i'm use
> https://github.com/bvanassche/ib_srp-backport/ for srp drivers on my
> linux server.
> Now i'm using 3.8.6, does i need something from
> https://github.com/bvanassche/ib_srp-backport/ or all patches already
> applied in upstream?
Unfortunately not all patches present in the ib_srp-backport project are
already upstream. If you want to avoid that in a multipath setup sooner
or later failover or failback fails with a SCSI device in the offline
state you will still need the ib_srp-backport project. I'm currently
working on converting that project into a new patch series intended for
inclusion in the mainline kernel.
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
next prev parent reply other threads:[~2013-04-08 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 8:00 linux 3.8.6 and srp backports Vasiliy Tolstov
[not found] ` <CACaajQu0OHOz0Ok-SkxHWPpTBEfRjNFGrPF8z5HX0bdq+sgXeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-08 8:23 ` Bart Van Assche [this message]
[not found] ` <51627E94.9010104-HInyCGIudOg@public.gmane.org>
2013-04-08 10:18 ` Vasiliy Tolstov
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=51627E94.9010104@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=v.tolstov-+9FY0jupvH6HXe+LvDLADg@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.