public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Why no SG support for isoc
Date: Tue, 7 Dec 2021 22:24:41 +0000	[thread overview]
Message-ID: <e58d3323-eb21-5c59-daa8-230b91082748@synopsys.com> (raw)

Hi,

I came across this change fe2072cc1768 ("usb/hcd: Ensure scatter-gather
is not used for isoc transfers") and wonder why it was made. The
description doesn't explain much. I was trying to look for the archived
conversation about this but couldn't find it.

Can someone help explain why we enforce this to all hosts? Or help point
to the archived conversation with the full explanation?

Thanks,
Thinh

             reply	other threads:[~2021-12-07 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 22:24 Thinh Nguyen [this message]
2021-12-08  2:52 ` Why no SG support for isoc Alan Stern
2021-12-08  3:32   ` Thinh Nguyen

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=e58d3323-eb21-5c59-daa8-230b91082748@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox