public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Greg KH <gregkh@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH RFC] maxSize option for usb-serial to increase max endpoint buffer size
Date: Mon, 12 Jun 2006 15:27:26 -0700	[thread overview]
Message-ID: <448DEA4E.7000707@goop.org> (raw)
In-Reply-To: <20060531203803.GA7735@suse.de>

Greg KH wrote:
> I've been working with Ken on getting this driver to work better
> (meaning faster).  Here's the latest version (without your new device id
> added).  Care to test it out and let me know if it works or not?
>   
I've been exercising this fairly heavily for the last few hours, and it 
looks pretty solid - no problems at all.

    J

  parent reply	other threads:[~2006-06-12 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 20:25 [PATCH RFC] maxSize option for usb-serial to increase max endpoint buffer size Jeremy Fitzhardinge
2006-05-31 20:38 ` Greg KH
2006-05-31 20:59   ` Jeremy Fitzhardinge
2006-06-12 22:27   ` Jeremy Fitzhardinge [this message]
2006-06-14 23:45     ` Greg KH

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=448DEA4E.7000707@goop.org \
    --to=jeremy@goop.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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