From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "C.L. Tien - ??????" <cltien@cmedia.com.tw>,
Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH]: cmpci 6.82 released
Date: Thu, 29 Apr 2004 16:55:38 -0300 [thread overview]
Message-ID: <20040429195538.GD20141@logos.cnet> (raw)
In-Reply-To: <20040429194635.GB20141@logos.cnet>
On Thu, Apr 29, 2004 at 04:46:35PM -0300, Marcelo Tosatti wrote:
> On Thu, Apr 15, 2004 at 01:15:31AM +0800, C.L. Tien - ?????? wrote:
> > Hi,
> >
> > I made several changes for cmpci.6.77, so the version is now 6.82.
> >
> > The patch is mostly from kernel 2.6, which change to support newer gcc,
> > fix possible security hole. I also use the same include files for both
> > kernel versions.
> >
> > The cmpci-6.82-patch2.4.tar.bz2 is made from official kernel 2.4.25, but should be able to patch other 2.4 kernel.
> >
> > The cmpci-6.82-patch2.6.tar.bz2 is from official kernel 2.6.5, it will
> > show error when patch cmpci.c for kernel 2.6.4 or earlier, that's ok.
>
> C.L. Tien,
>
> I see your fixes have not yet been merged into v2.6.x mainline.
>
> I dont know the card very well, but the fixes alright.
>
> Andrew, maybe you can merge this in -mm?
C.L. Tien,
Forgot to mention that it would be very nice if you could separate the update into
several patches (with a changelog for each).
next prev parent reply other threads:[~2004-04-29 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 17:15 [PATCH]: cmpci 6.82 released C.L. Tien - 田承禮
2004-04-16 20:43 ` Adrian Bunk
2004-04-29 19:46 ` Marcelo Tosatti
2004-04-29 19:55 ` Marcelo Tosatti [this message]
2004-04-29 20:40 ` Jeff Garzik
2004-05-02 19:33 ` Willy Tarreau
2004-04-29 21:14 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-04-17 1:52 C.L. Tien - 田承禮
2004-04-17 19:40 ` Adrian Bunk
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=20040429195538.GD20141@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cltien@cmedia.com.tw \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox