From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] ldd01: remove all -m32/-m64 logic
Date: Fri, 19 Sep 2014 14:41:23 +0200 [thread overview]
Message-ID: <20140919124122.GB29490@rei> (raw)
In-Reply-To: <79378c28685642da5fa56683fc1385eca55d1328.1410513010.git.jstancek@redhat.com>
Hi!
> and build all binaries with same CFLAGS as rest of LTP build.
Looks good to me. The only thing I'm not sure about is whether the ldd
files shouldn't be reather treated as a data files (and therefore
installed under testcases/bin/data/ldd/ as described in 2.1.2 of the
Test writing guidelines).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Slashdot TV. Video for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-09-19 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 9:14 [LTP] [PATCH] ldd01: remove all -m32/-m64 logic Jan Stancek
2014-09-12 9:33 ` Jan Stancek
2014-09-19 12:41 ` chrubis [this message]
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=20140919124122.GB29490@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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