From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Devesh Sharma <devesh.sharma-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ocrdma failure in 4.4.0-rc5
Date: Wed, 23 Dec 2015 12:59:04 -0500 [thread overview]
Message-ID: <567AE0E8.70107@redhat.com> (raw)
In-Reply-To: <CANjDDBiJAyfS7wFr9yYs7fAnn1-h9t1JH9s1LDf-Q8RYk=Ayyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On 12/20/2015 11:29 PM, Devesh Sharma wrote:
> Hi Dough,
>
> Thanks for your note.
>
> We will root cause the issue asap and get back to you with the fix.
Ping. Any update?
> -Regards
> Devesh
>
> On Sun, Dec 20, 2015 at 1:41 AM, Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> Hi Devesh,
>>
>> Testing 4.4.0-rc5, the ocrdma driver is failing for me (100% reliably).
>> If you have vlans off of the main device, this is what I get from the
>> Fedora rawhide 4.4.0-rc5 kernel:
>>
>>
>> --
>> Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> GPG KeyID: 0E572FDD
>>
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-12-23 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 20:11 ocrdma failure in 4.4.0-rc5 Doug Ledford
[not found] ` <5675BA00.5060101-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-21 4:29 ` Devesh Sharma
[not found] ` <CANjDDBiJAyfS7wFr9yYs7fAnn1-h9t1JH9s1LDf-Q8RYk=Ayyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-23 17:59 ` Doug Ledford [this message]
[not found] ` <567AE0E8.70107-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-23 18:53 ` Devesh Sharma
[not found] ` <CANjDDBibF9eR-uumY3rzckeDfDE6CfBQsAAdkZVWAitdviW2FQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-23 19:22 ` Doug Ledford
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=567AE0E8.70107@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=devesh.sharma-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org \
--cc=linux-rdma-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 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.