From: Stephan von Krawczynski <skraw@ithnet.com>
To: Luca Montecchiani <m.luca@iname.com>
Cc: marcelo@conectiva.com.br, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17-pre5
Date: Fri, 07 Dec 2001 01:12:53 +0100 [thread overview]
Message-ID: <200112070012.BAA24810@webserver.ithnet.com> (raw)
In-Reply-To: <3C0FD89A.10B28C7B@iname.com>
> Hisax compile fix :
>
> --- drivers/isdn/hisax/config.c.orig Thu Dec 6 21:34:23 2001
> +++ drivers/isdn/hisax/config.c Thu Dec 6 21:34:31 2001
> @@ -485,7 +485,7 @@
> if (strlen(str) < HISAX_IDSIZE)
> strcpy(HiSaxID, str);
> else
> - printk(KERN_WARNING "HiSax: ID too long!")
> + printk(KERN_WARNING "HiSax: ID too long!");
> } else
> strcpy(HiSaxID, "HiSax");
>
>
Ah, shit. Thanks luca, this was my fault. Never cut'n'paste via mouse
on important occasions.
Sorry guys, this was my fault, not Marcelo's.
BTW, for the further ongoing of this patch, I ran into the question if
MODULE_PARM(type, "1-(16)i");
would be a valid statement. I guess not. But if not, could some kind
soul please explain to me how to get rid of the braces "(" ")" given
in definitions from CONFIG stuff.
E.g.:
CONFIG_ME_BEING_DUMB (16)
entering above MODULE_PARM contruction via a definition. I searched
the source tree a bit, but did not find any hints.
Regards,
Stephan
PS: I _will_ re-check the next patches several times, I swear ... :-)
next prev parent reply other threads:[~2001-12-07 0:30 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 20:44 Linux 2.4.17-pre5 Luca Montecchiani
2001-12-07 0:12 ` Stephan von Krawczynski [this message]
2001-12-07 3:43 ` Keith Owens
2001-12-07 11:55 ` Stephan von Krawczynski
2001-12-07 13:35 ` Keith Owens
2001-12-07 14:25 ` Stephan von Krawczynski
2001-12-07 16:39 ` Linux 2.4.17-pre5 / Have fun with make Stephan von Krawczynski
2001-12-07 22:21 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 17:39 Linux 2.4.17-pre5 Marcelo Tosatti
2001-12-06 19:07 ` Alan Cox
2001-12-06 23:38 ` Dave Jones
2001-12-07 0:09 ` Alan Cox
2001-12-08 10:46 ` Rusty Russell
2001-12-09 0:31 ` Alan Cox
2001-12-09 1:58 ` Rusty Russell
2001-12-09 2:35 ` Davide Libenzi
2001-12-09 6:20 ` Rusty Russell
2001-12-09 16:24 ` Alan Cox
2001-12-09 19:48 ` Davide Libenzi
2001-12-09 22:44 ` Mike Kravetz
2001-12-09 23:50 ` Davide Libenzi
2001-12-09 23:57 ` Alan Cox
2001-12-19 22:16 ` Pavel Machek
2001-12-20 19:10 ` Davide Libenzi
2001-12-09 16:16 ` Alan Cox
2001-12-10 0:21 ` Rusty Russell
2001-12-10 0:41 ` Alan Cox
2001-12-10 2:10 ` Martin J. Bligh
2001-12-10 5:40 ` Rusty Russell
2001-12-10 5:31 ` Rusty Russell
2001-12-10 8:28 ` Alan Cox
2001-12-10 23:12 ` James Cleverdon
2001-12-10 23:30 ` Alan Cox
2001-12-11 9:16 ` Robert Varga
2001-12-11 9:23 ` David Weinehall
2001-12-11 9:00 ` Eric W. Biederman
2001-12-11 23:14 ` Alan Cox
2001-12-09 19:38 ` Marcelo Tosatti
2001-12-09 9:47 ` arjan
2001-12-07 16:07 ` Marcelo Tosatti
2001-12-06 19:18 ` Matthias Andree
2001-12-06 19:05 ` Marcelo Tosatti
2001-12-06 21:14 ` Ben Greear
2001-12-06 21:58 ` David S. Miller
2001-12-06 22:24 ` Matthias Andree
2001-12-09 10:10 ` Eran Man
2001-12-06 20:14 ` Rik van Riel
2001-12-06 20:22 ` Jeff Garzik
2001-12-06 20:58 ` David S. Miller
2001-12-08 4:56 ` M. Edward Borasky
2001-12-08 5:41 ` David S. Miller
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=200112070012.BAA24810@webserver.ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.luca@iname.com \
--cc=marcelo@conectiva.com.br \
/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