From: John Kacur <jkacur@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Nicolas Saenz Julienne <nsaenzju@redhat.com>,
linux-rt-users@vger.kernel.org, williams@redhat.com
Subject: Re: [PATCH 1/2] oslat: Remove redundant include
Date: Fri, 9 Jul 2021 14:08:45 -0400 (EDT) [thread overview]
Message-ID: <b207f7f-3fff-4020-9727-58e2ec8ac6cb@redhat.com> (raw)
In-Reply-To: <YOXoFUS8TljxgPYn@t490s>
On Wed, 7 Jul 2021, Peter Xu wrote:
> On Wed, Jul 07, 2021 at 10:48:48AM +0200, Nicolas Saenz Julienne wrote:
> > inttypes.h is already included above.
> >
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
> --
> Peter Xu
>
>
Thanks, added
next prev parent reply other threads:[~2021-07-09 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 8:48 [PATCH 1/2] oslat: Remove redundant include Nicolas Saenz Julienne
2021-07-07 8:48 ` [PATCH 2/2] oslat: Don't take trace_threshold into account during preheat Nicolas Saenz Julienne
2021-07-07 17:45 ` Peter Xu
2021-07-09 18:09 ` John Kacur
2021-07-09 18:08 ` John Kacur
2021-07-07 17:44 ` [PATCH 1/2] oslat: Remove redundant include Peter Xu
2021-07-09 18:08 ` John Kacur [this message]
2021-07-09 18:08 ` John Kacur
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=b207f7f-3fff-4020-9727-58e2ec8ac6cb@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=nsaenzju@redhat.com \
--cc=peterx@redhat.com \
--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