From: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
To: Marcelo Tosatti <marcelo@hera.kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: linux-2.4.21 released , No changelog for sym53c8xx_2 mods ?
Date: Sun, 15 Jun 2003 15:49:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0306151540080.13925@filesrv1.baby-dragons.com> (raw)
In-Reply-To: <200306131453.h5DErX47015940@hera.kernel.org>
Hello Marcello , I have a problem with the lack of changelog
entries concerning the sym53c8xx_2 driver . There are none .
And yet there has been changes to the driver tree .
As you'll note this includes the change log file in the driver
tree as well . I have grep'd and manually viewed the change logs
from kernel.org with no mention of these changes noted .
Also Mr. Roudier put out a patch set versioned sym-2.1.19-pre3 on
20031123 which has never been insterted into 2.4 (possibly at his
request) . I have been using this patch since the above date
without difficulty in every pre , rc & release since that date .
Tia , JimL
8 -rw-r--r-- 1 573 573 6015 Dec 21 2001 ChangeLog.txt
12 -rw-r--r-- 1 573 573 10274 Nov 28 2002 sym_malloc.c
76 -rw-r--r-- 1 573 573 73259 Nov 28 2002 sym_glue.c
60 -rw-r--r-- 1 573 573 53467 Nov 28 2002 sym_fw2.h
48 -rw-r--r-- 1 573 573 48334 Nov 28 2002 sym_fw1.h
12 -rw-r--r-- 1 573 573 10424 Nov 28 2002 sym53c8xx.h
152 -rw-r--r-- 1 573 573 149323 Jun 13 10:51 sym_hipd.c
--
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+
next prev parent reply other threads:[~2003-06-15 19:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 14:53 linux-2.4.21 released Marcelo Tosatti
2003-06-13 16:56 ` Stefan Foerster
2003-06-13 16:56 ` Damian Kolkowski
2003-06-13 17:37 ` Stephan von Krawczynski
2003-06-13 17:19 ` Damian Kołkowski
2003-06-13 17:49 ` Alan Cox
2003-06-13 17:45 ` Damian Kolkowski
2003-06-13 18:36 ` Damian Kołkowski
2003-06-13 21:04 ` Daniel Egger
2003-06-13 21:31 ` Damian Kołkowski
2003-06-15 14:29 ` Daniel Egger
2003-06-14 15:59 ` Krzysiek Taraszka
2003-06-14 16:16 ` Damian Kołkowski
2003-06-13 18:10 ` Serguei Miridonov
2003-06-13 17:22 ` Matthias Andree
2003-06-13 17:29 ` Christoph Hellwig
2003-06-14 21:35 ` Diego Calleja García
2003-06-14 21:58 ` Ramón Rey Vicente
2003-06-15 12:02 ` Matthias Andree
2003-06-13 18:56 ` Ramón Rey Vicenteey Vicente
2003-06-13 20:03 ` Robert Love
2003-06-13 20:27 ` Ramón Rey Vicente
2003-06-13 21:50 ` J.A. Magallon
2003-06-14 7:31 ` Wiktor Wodecki
2003-06-13 19:14 ` Udo A. Steinberg
2003-06-13 19:24 ` Ross Biro
2003-06-14 2:02 ` Andrea Arcangeli
2003-06-14 4:28 ` Ben Collins
2003-06-14 15:36 ` CJ
2003-06-14 15:54 ` Jörn Engel
2003-06-14 16:29 ` CJ
2003-06-15 19:06 ` Jörn Engel
2003-06-15 19:49 ` Mr. James W. Laferriere [this message]
2003-06-16 22:22 ` Lukasz Trabinski
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=Pine.LNX.4.56.0306151540080.13925@filesrv1.baby-dragons.com \
--to=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@hera.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;
as well as URLs for NNTP newsgroup(s).