All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bollinger, Seth" <Seth.Bollinger@digi.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>
Subject: Re: Bug: VHCI + USB 3.0
Date: Mon, 8 Apr 2019 19:12:19 +0000	[thread overview]
Message-ID: <C22C24B7-A1A1-44E4-9559-ED576ABE8CFF@digi.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1904081453480.1440-100000@iolanthe.rowland.org>

> On Apr 8, 2019, at 1:59 PM, Alan Stern <stern@rowland.harvard.edu<mailto:stern@rowland.harvard.edu>> wrote:

> No, that trace did not show any failure.  Did you see the corresponding
> error messages in the kernel log while you were collecting the trace?
> Maybe you can try again.

I’m certain the last trace I sent should have contained the read.

bulk A 000004bf ty 03 st 00000000 T 3584 L 0 ch 00000081 ep 1 fl 0
BI completion: st 0 stat -75 AL 0 ec 0 returning -75

> PS: Why doesn't your email client insert some sort of "reply indent"
> string, such as "> "?  Looking at the messages you send, it's not so
> easy to tell which parts were written by you and which you are replying
> to.

My apologies.  I tested it using my gmail and I see the “> “, so I thought it was set up correctly.  Unfortunately my company doesn’t give me a client that will easily support that.  I’ll try and do it by hand.



  reply	other threads:[~2019-04-08 19:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 19:19 Bug: VHCI + USB 3.0 Bollinger, Seth
2019-04-05 21:01 ` Alan Stern
2019-04-05 21:30   ` Bollinger, Seth
2019-04-06 15:34     ` Alan Stern
2019-04-06 15:57       ` Bollinger, Seth
2019-04-06 16:08         ` Alan Stern
2019-04-08 12:39           ` Bollinger, Seth
2019-04-08 14:33             ` Alan Stern
2019-04-08 14:48               ` Bollinger, Seth
2019-04-08 16:29               ` Bollinger, Seth
2019-04-08 17:23                 ` Alan Stern
2019-04-08 18:28                   ` Bollinger, Seth
2019-04-08 18:59                     ` Alan Stern
2019-04-08 19:12                       ` Bollinger, Seth [this message]
2019-04-08 19:50                         ` Alan Stern
2019-04-09 13:30                         ` Bollinger, Seth
2019-04-09 14:51                           ` Bollinger, Seth
2019-04-09 13:30                         ` Bollinger, Seth
2019-04-09 15:19                           ` Alan Stern
2019-04-09 15:56                             ` Ming Lei
2019-04-09 19:06                               ` Alan Stern
2019-04-09 19:13                                 ` Bollinger, Seth
2019-04-09 19:57                                   ` Alan Stern
2019-04-10  8:02                                     ` Oliver Neukum
2019-04-10 14:22                                       ` Alan Stern
2019-04-10 13:50                                   ` Bollinger, Seth
2019-04-10 14:52                                     ` Alan Stern
2019-04-10 14:52                                       ` Alan Stern
2019-04-08 18:39                   ` Bollinger, Seth
2019-04-12 18:01 Alan Stern
2019-04-12 18:01 ` Alan Stern
2019-04-13 11:37 Bollinger, Seth
2019-04-13 11:37 ` Bollinger, Seth

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=C22C24B7-A1A1-44E4-9559-ED576ABE8CFF@digi.com \
    --to=seth.bollinger@digi.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.