Small patch for sbpcd on 2.1.37-pre4 (and small question)

Carlo E. Prelz (fluido@marktest.pt)
Sun, 4 May 1997 20:23:40 +0100 (WET DST)


Hi. My gcc (2.7.2.1) refused to compile drivers/cdrom/sbpcd.c, complaining
that it did not appreciate pre-processor commands in the middle of macros.
The following patch solved the problem:

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

--- sbpcd.c~ Sun May 4 19:18:26 1997
+++ sbpcd.c Sun May 4 19:38:28 1997
@@ -5285,11 +5285,11 @@
* bytes above).
*
*/
-__initfunc(
#if (SBPCD_ISSUE-1)
-static
+__initfunc(static void sbpcd_setup(const char *s, int *p))
+#else
+__initfunc(void sbpcd_setup(const char *s, int *p))
#endif
-void sbpcd_setup(const char *s, int *p))
{
setup_done++;
msg(DBG_INI,"sbpcd_setup called with %04X,%s\n",p[1], s);

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

While I am talking about this, why is it that, since about 10 releases
ago, am I getting flurries of the following types of messages:

_isofs_bmap: block>= EOF(2,4096)

(where the last numbers may vary). I am getting one of those if I use
the auto-completion feature of bash, while looking at directories
within a mounted CDrom. That is,

cd /cdrom/ker<TAB><TAB>

and before the command is completed (correctly), the above message
appears.

I also get about two pages of these sometimes after starting the machine,
without touching the CDrom (the CDrom led lights while the messages are
generated). Otherwise, I can read the CDrom OK.

Can I sleep at nights?

Carlo

--
  *                                          ...Ma appena fuori tutto e' gomma,
* K * Carlo E. Prelz - fluido@marktest.pt     tutto e' cicca impiastricciata...
  *                                     (Marco Zappa-Niente cicca nella scuola)