All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
	Robert LeBlanc <robert-4JaGZRWAfWbajFs6igw21g@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"leon-2ukJVAZIZ/Y@public.gmane.org"
	<leon-2ukJVAZIZ/Y@public.gmane.org>
Subject: Re: MLX5 iSER issue on 4.6?
Date: Sun, 29 May 2016 20:32:35 +0300	[thread overview]
Message-ID: <574B27B3.707@mellanox.com> (raw)
In-Reply-To: <574AE1AB.9050501-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>

>
> Can you report if Mellanox plans to fix it in FW or should we work
> around in the driver?

I investigated it today, and the bug isn't in the FW.
there is a bug in the casting of device caps.
I have a patch that I'll send tomorrow.
Thanks for reporting and helping with this issue,
Max.

>
> Thanks,
> Sagi.
--
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:[~2016-05-29 17:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 22:32 MLX5 iSER issue on 4.6? Robert LeBlanc
     [not found] ` <CAANLjFpPoynQeBiQjZ=2RA1YHaNp3jZKtavZ5URWcsJu+x85vA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-29  6:58   ` Sagi Grimberg
     [not found]     ` <574A930E.6030507-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-05-29 12:05       ` Max Gurtovoy
     [not found]         ` <574ADB25.8080903-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-05-29 12:33           ` Sagi Grimberg
     [not found]             ` <574AE1AB.9050501-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-05-29 17:32               ` Max Gurtovoy [this message]

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=574B27B3.707@mellanox.com \
    --to=maxg-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=leon-2ukJVAZIZ/Y@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=robert-4JaGZRWAfWbajFs6igw21g@public.gmane.org \
    --cc=sagi-NQWnxTmZq1alnMjI0IkVqw@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.