From: Gene Heskett <gene.heskett@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: David Newall <davidn@davidnewall.com>, 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 12:47:47 -0500 [thread overview]
Message-ID: <200802221247.48178.gene.heskett@gmail.com> (raw)
In-Reply-To: <20080222100223.GA4711@1wt.eu>
On Friday 22 February 2008, Willy Tarreau wrote:
>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
I was not successfull at testing it last night, even locally built versions of
roadnav are segfaulting for me now. Something still missing from the wxGTK
camp I believe.
Feb 21 21:05:49 coyote kernel: [799800.925900] roadnav[30556]: segfault at
00000041 eip 494b9d2f esp bf9d8570 error 4
But that may was well be swahili to me. And it may run half an hour before it
does it. It seems to be related to trying to pull missing TIGER-line maps.
Its also a serious cpu hog when its running.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If the rich could pay the poor to die for them, what a living the poor
could make!
next prev parent reply other threads:[~2008-02-22 17:50 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
2008-02-22 17:47 ` Gene Heskett [this message]
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=200802221247.48178.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=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