From: Willy Tarreau <w@1wt.eu>
To: David Newall <davidn@davidnewall.com>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4: Back-port of pl2303.c from 2.6.24.1
Date: Fri, 22 Feb 2008 11:02:23 +0100 [thread overview]
Message-ID: <20080222100223.GA4711@1wt.eu> (raw)
In-Reply-To: <47BE267E.3070508@davidnewall.com>
On Fri, Feb 22, 2008 at 12:03:50PM +1030, David Newall wrote:
> Greg KH wrote:
> > On Thu, Feb 21, 2008 at 10:00:58PM +0100, Willy Tarreau wrote:
> >
> >> I too agree to merge, it especially since it fixed several problems
> >> for David. However, I would like to know first if the same problems
> >> also happen with the 2.6 driver or if it is OK. The risk is getting
> >> 2.4 fixed and not 2.6, which could cause regressions for people upgrading
> >> from 2.4 to 2.6. Of course, a regression on a USB-serial adapter is
> >> not dramatic, but it's a general principle to keep in mind that 2.6
> >> should be safe (or at least actively being fixed) when merging driver
> >> changes in 2.4.
> >>
> >
> > As far as I can tell, this was a backport of the current 2.6 driver, so
> > it should not have fixes that are not already in 2.6.
> >
> > David, is that true?
> >
>
> That is true.
OK that's perfect. I will merge it.
Cheers,
Willy
next prev parent reply other threads:[~2008-02-22 10:02 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
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 [this message]
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=20080222100223.GA4711@1wt.eu \
--to=w@1wt.eu \
--cc=davidn@davidnewall.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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.