cvs commit: src/sys/compat/linprocfs linprocfs.c

[Scott Long]

Alexander Leidinger wrote:
> Quoting Sam Leffler <sam at errno.com> (Sat, 20 Jan 2007 12:05:04 -0800):
> 
>> Scott Long wrote:
>>> Alexander Leidinger wrote:
>>>> netchild    2007-01-20 19:32:23 UTC
>>>>
>>>>   FreeBSD src repository
>>>>
>>>>   Modified files:
>>>>     sys/compat/linprocfs linprocfs.c   Log:
>>>>   Fix tinderbox build on amd64.
>>>>     Revision  Changes    Path
>>>>   1.104     +2 -2      src/sys/compat/linprocfs/linprocfs.c
>>> Try the following instead:
> 
> I try tomorrow. Thanks!
> 
>>> --- linprocfs.c 20 Jan 2007 19:32:23 -0000      1.104
>>> +++ linprocfs.c 20 Jan 2007 19:46:29 -0000
>>> @@ -474,8 +474,8 @@
>>>                 state = 'R';
>>>
>>>                 if (ratelimit == 0) {
>>> -                       printf("linprocfs: don't know how to handle
>>> unknown FreeBSD state %d/%jd, mapping to R\n",
>>> -                           kp.ki_stat, (intmax_t)sizeof(linux_state));
>>> +                       printf("linprocfs: don't know how to handle
>>> unknown FreeBSD state %d/%zd, mapping to R\n",
>>> +                           kp.ki_stat, sizeof(linux_state));
>>>                         ++ratelimit;
>>>                 }
>>>         } else
>>>
>>>
>> Are the kernel prinf extensions documented anywhere (don't see 'em in
>> printf(9))?  I always forget and have to resort to the code...
> 
> In the reply to the tinderbox mail I asked if there are some docs which
> provide info which printf-identifier to use in which (common)
> situation. I think this would be very useful (and can be provided in
> the wiki if it doesn't fit into a man page).
> 
> Bye,
> Alexander.
> 

I use printf.3 for reference.  The kernel printf is only a subset, but
it implements enough for the userland docs to be useful.  For backup, I
recommend using bde@

Scott