public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Newall <davidn@davidnewall.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [PATCH] 2.4: Back-port of pl2303.c from 2.6.23.14
Date: Sat, 02 Feb 2008 23:41:20 +1030	[thread overview]
Message-ID: <47A46BF8.6030306@davidnewall.com> (raw)
In-Reply-To: <20080202074406.GA31516@1wt.eu>

Hi Willy,

Willy Tarreau wrote:
> Based on the above conditions, I'd like you to tell Greg and I if you
> consider it worth to merge this backport in 2.4 now. From my point of
> view, your work looks OK but I want your feedback as a user (and not
> as the backporter), then Greg's approval.

The data loss I experienced did go away with the back-port, but I think
that was because of the bigger buffers, rather than any true fix. Other
than the extra product ids, it won't really change anything. I'm hoping
the additional work I've done since then will correct the underlying
fault. (Wish I could get some feedback on it.) I'd be happy for you to
wait for that.

  reply	other threads:[~2008-02-02 13:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  0:50 [PATCH] 2.4: Back-port of pl2303.c from 2.6.23.14 David Newall
2008-02-02  7:44 ` Willy Tarreau
2008-02-02 13:11   ` David Newall [this message]
2008-02-02 14:57     ` Willy Tarreau
2008-02-21 20:21     ` [PATCH] 2.4: Back-port of pl2303.c from 2.6.24.1 David Newall
2008-02-21 20:30       ` David Newall
2008-02-21 20:36       ` Greg KH
2008-02-21 21:00         ` Willy Tarreau
2008-02-21 21:33           ` Greg KH
2008-02-22  1:33             ` David Newall
2008-02-22 10:02               ` Willy Tarreau
2008-02-22 17:47                 ` Gene Heskett
2008-03-19 14:24                   ` David Newall

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=47A46BF8.6030306@davidnewall.com \
    --to=davidn@davidnewall.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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