From: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
Clark Williams <williams@redhat.com>
Subject: Re: [PATCH] rt-tests: Use gettid from rt-utils.c everywhere
Date: Wed, 26 Jun 2019 13:25:47 +0200 [thread overview]
Message-ID: <20190626112547.rhqgypbepi7mxlth@linutronix.de> (raw)
In-Reply-To: <20190626110838.7800-1-jkacur@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
Hi,
On Wed, Jun 26, 2019 at 01:08:38PM +0200, John Kacur wrote:
> gettid is defined in rt-utils, so we should use that everywhere instead
> of defining a separate macro in each test for it.
looks good to me.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-06-26 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 11:08 [PATCH] rt-tests: Use gettid from rt-utils.c everywhere John Kacur
2019-06-26 11:12 ` Sebastian Siewior
2019-06-26 11:25 ` Kurt Kanzenbach [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=20190626112547.rhqgypbepi7mxlth@linutronix.de \
--to=kurt.kanzenbach@linutronix.de \
--cc=bigeasy@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).