netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <mlord@pobox.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: "Sarah Sharp" <sarah.a.sharp@linux.intel.com>,
	"Bjørn Mork" <bjorn@mork.no>,
	"David Laight" <David.Laight@aculab.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"David Miller" <davem@davemloft.net>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Nyman, Mathias" <mathias.nyman@intel.com>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Freddy Xin" <freddy@asix.com.tw>
Subject: Re: [PATCH RFC 1/1] usb: Tell xhci when usb data might be misaligned
Date: Sat, 01 Feb 2014 15:05:21 -0500	[thread overview]
Message-ID: <52ED5381.2010106@pobox.com> (raw)
In-Reply-To: <CACVXFVOynsojKo+aukHY4q+MkEyhHXC0=OpN0ysu0TGuUjY8sA@mail.gmail.com>

On 14-02-01 09:18 AM, Ming Lei wrote:
>
> Even real regressions are easily/often introduced, and we are discussing
> how to fix that. I suggest to unset the flag only for the known buggy
> controllers.


It is not the controllers that are particularly "buggy" here.
But rather the drivers and design of parts of the kernel.

Cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com

  reply	other threads:[~2014-02-01 20:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 21:18 [PATCH RFC 1/1] usb: Tell xhci when usb data might be misaligned Sarah Sharp
2014-01-30 21:39 ` Mark Lord
2014-01-30 21:42   ` Mark Lord
2014-01-30 21:43 ` Alan Stern
2014-01-30 21:48   ` Mark Lord
2014-01-30 21:55   ` Sarah Sharp
2014-01-30 22:05     ` Bjørn Mork
2014-01-30 22:07     ` Alan Stern
2014-01-30 21:50 ` Bjørn Mork
2014-01-30 22:15   ` Sarah Sharp
2014-01-31  0:17     ` Ming Lei
2014-01-31 19:00       ` Sarah Sharp
2014-02-01  7:54         ` Ming Lei
2014-02-01 13:30           ` Mark Lord
2014-02-01 14:18             ` Ming Lei
2014-02-01 20:05               ` Mark Lord [this message]
     [not found]                 ` <52ED5381.2010106-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2014-02-03  9:54                   ` David Laight
2014-02-03 17:56                     ` Sarah Sharp
2014-02-03 17:55                   ` Sarah Sharp
2014-01-31 15:22     ` David Laight
2014-01-31 10:14 ` David Laight
2014-01-31 13:21   ` Peter Stuge
2014-01-31 13:52     ` David Laight
  -- strict thread matches above, loose matches on Subject: below --
2014-01-30 16:00 David Laight
     [not found] ` <063D6719AE5E284EB5DD2968C1650D6D0F6B5486-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-01-30 16:17   ` Peter Stuge
     [not found]     ` <20140130161721.25560.qmail-Y+HMSxxDrH8@public.gmane.org>
2014-01-30 16:30       ` David Laight
     [not found]         ` <063D6719AE5E284EB5DD2968C1650D6D0F6B553D-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-01-30 16:35           ` Peter Stuge
2014-01-31  9:30             ` David Laight

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=52ED5381.2010106@pobox.com \
    --to=mlord@pobox.com \
    --cc=David.Laight@aculab.com \
    --cc=bjorn@mork.no \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=freddy@asix.com.tw \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=ming.lei@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).