mirror of https://gerrit.osmocom.org/libosmocore
utils: remove misleading comments for osmo_hexdump[_nospc]_c()
The buffer is allocated dynamically on heap, so there is no such limitation of 4096 bytes / 1365 characters. Change-Id: I960dd6a53123fd4209ef6e61dcd0d22e4005e397
This commit is contained in:
parent
34907fe6e1
commit
6dce2cbc1e
|
@ -407,9 +407,6 @@ char *osmo_hexdump(const unsigned char *buf, int len)
|
|||
*
|
||||
* This function will print a sequence of bytes as hexadecimal numbers,
|
||||
* adding one space character between each byte (e.g. "1a ef d9")
|
||||
*
|
||||
* The maximum size of the output buffer is 4096 bytes, i.e. the maximum
|
||||
* number of input bytes that can be printed in one call is 1365!
|
||||
*/
|
||||
char *osmo_hexdump_c(const void *ctx, const unsigned char *buf, int len)
|
||||
{
|
||||
|
@ -446,9 +443,6 @@ char *osmo_hexdump_nospc(const unsigned char *buf, int len)
|
|||
*
|
||||
* This function will print a sequence of bytes as hexadecimal numbers,
|
||||
* without any space character between each byte (e.g. "1aefd9")
|
||||
*
|
||||
* The maximum size of the output buffer is 4096 bytes, i.e. the maximum
|
||||
* number of input bytes that can be printed in one call is 2048!
|
||||
*/
|
||||
char *osmo_hexdump_nospc_c(const void *ctx, const unsigned char *buf, int len)
|
||||
{
|
||||
|
|
Loading…
Reference in New Issue