On Sat, Oct 13, 2007 at 07:16:55PM +0000, Alex Riesen wrote:Ok. Yes this has been spotted and fixed already. Yes this is intentional, there should be at least on string in the usagestr array. the reason is that usage() is a wrapper around a callback, and I suppose it's used by some GUI's or anything like that. FWIW you can rework the .c like this: pos =3D 0; /* and not pos =3D sb.len */ replace the strbuf_add* by the equivalents: pos +=3D printf("...."); and tada, you're done. Note that in the most recent version, I also deal with a OPTION_CALLBACK that passes the value to a callback. Cheers, --=20 =C2=B7O=C2=B7 Pierre Habouzit =C2=B7=C2=B7O madcoder@debia= n.org OOO http://www.madism.org
| Kok, Auke | Re: -mm merge plans for 2.6.23 - ioat/dma engine |
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Matthew Garrett | [PATCH] Remove process freezer from suspend to RAM pathway |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
git: | |
