From: Frank Rowand <frank.rowand@am.sony.com>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
"Rowand, Frank" <Frank_Rowand@sonyusa.com>,
rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH RT-TESTS 0/3] A few Makefile clean-ups
Date: Fri, 8 Feb 2013 15:07:42 -0800 [thread overview]
Message-ID: <5115853E.8050004@am.sony.com> (raw)
In-Reply-To: <1360334855-10176-1-git-send-email-jkacur@redhat.com>
On 02/08/13 06:47, John Kacur wrote:
> From: John Kacur <jkacur@redhat.com>
>
> I have few simple build clean-ups, which should be uncontroversial
> for the rt-tests suite
>
> John Kacur (3):
> Makefile: Don't tag tmp files created when making a release
> Makefile: Add tmp dir to distclean and "make release" call distclean
> Makefile: Add BUILDROOT and SPECS to the dirs to remove for distclean
>
> Makefile | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
All three patches:
Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
Tested-by: Frank Rowand <frank.rowand@am.sony.com>
With the caveat that "make rpm" does not complete on my build system
due to a missing numactl-devel dependency.
Even without "make rpm" completing, it creates the extra objects
that patch 3 removes, so I think my testing is still valid.
-Frank
prev parent reply other threads:[~2013-02-08 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 14:47 [PATCH RT-TESTS 0/3] A few Makefile clean-ups John Kacur
2013-02-08 14:47 ` [PATCH RT-TESTS 1/3] Makefile: Don't tag tmp files created when making a release John Kacur
2013-02-08 14:47 ` [PATCH RT-TESTS 2/3] Makefile: Add tmp dir to distclean and "make release" call distclean John Kacur
2013-02-08 14:47 ` [PATCH RT-TESTS 3/3] Makefile: Add BUILDROOT and SPECS to the dirs to remove for distclean John Kacur
2013-02-08 23:07 ` Frank Rowand [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=5115853E.8050004@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=Frank_Rowand@sonyusa.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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