public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: alexey.kodanev@oracle.com
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] New core test of cgroups and extended attributes
Date: Thu, 16 May 2013 10:39:24 +0200	[thread overview]
Message-ID: <20130516083923.GA31149@rei> (raw)
In-Reply-To: <5194838B.2060104@oracle.com>

Hi!
> > I do not want to add custom printf() format strings on purpose, as that
> > would:
> >
> > 1) create confusion
> >
> > 2) possibly break the checks on the format done by compiler
> >
> > Anybody else has better idea?
> Since we're going to print buf in hex, may be we can use
> tst_resm_hex(flags, buf, buf_len, fmt, ...) to make it more descriptive?

Naming things right is hard. I agree that 'hex' should be part of the
name but ideally something like 'dump' or 'buf' should be there as well
at least in form of the first letter (to keep the name reasonably short).

tst_resm_bhex() or tst_resm_dhex() ?

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2013-05-16  8:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  9:40 [LTP] [PATCH] New core test of cgroups and extended attributes Alexey Kodanev
2013-05-15 12:38 ` chrubis
     [not found]   ` <51939CB6.3020808@oracle.com>
2013-05-15 14:56     ` chrubis
     [not found]       ` <5194838B.2060104@oracle.com>
2013-05-16  8:39         ` chrubis [this message]
     [not found]           ` <5194A887.3010204@oracle.com>
2013-05-16 10:06             ` chrubis
  -- strict thread matches above, loose matches on Subject: below --
2013-05-22 10:24 Alexey Kodanev
2013-05-22 14:26 ` chrubis
2013-05-23  7:09 Alexey Kodanev
2013-05-23 13:31 ` chrubis
2013-05-23 16:28 Alexey Kodanev
2013-05-24 12:20 Alexey Kodanev
2013-05-28 14:37 ` chrubis
     [not found]   ` <51A4C663.7010506@oracle.com>
2013-05-28 15:43     ` chrubis
2013-05-29 10:28 Alexey Kodanev
2013-05-30 18:55 ` chrubis

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=20130516083923.GA31149@rei \
    --to=chrubis@suse.cz \
    --cc=alexey.kodanev@oracle.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vasily.isaenko@oracle.com \
    /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