From: Punit Agrawal <punitagrawal@gmail.com>
To: jkacur@redhat.com
Cc: Punit Agrawal <punitagrawal@gmail.com>,
linux-rt-users@vger.kernel.org, punit1.agrawal@toshiba.co.jp
Subject: [PATCH 0/2] rteval: Miscellaneous fixes
Date: Thu, 9 Sep 2021 17:05:45 +0900 [thread overview]
Message-ID: <20210909080547.1331581-1-punitagrawal@gmail.com> (raw)
Hi,
Since the previous two patchsets fixing blockers[0], [1], I
encountered a couple of more benign issues - noticed when staring at
the generated report - summary.xml.
The first patch fixes a problem with incorrect detection of RT
kernels. I've tried to retain the old behaviour in case somebody is
still using older kernels. The change can be made more robust if
that's no longer needed.
The second patch fixes an issue with incorrect detection of init
system and container environment. This is a result of change in how
strings are treated in python3 (compared to python2).
As usual, all feedback welcome.
Thanks,
Punit
[0] https://lore.kernel.org/all/20210901080816.721731-1-punitagrawal@gmail.com/
[1] https://lore.kernel.org/all/20210902092452.726905-1-punitagrawal@gmail.com/
Punit Agrawal (2):
rteval: osinfo.py: Fix RT kernel detection
rteval: services.py: Fix incorrect detection of container environment
rteval/sysinfo/osinfo.py | 2 +-
rteval/sysinfo/services.py | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.32.0
next reply other threads:[~2021-09-09 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 8:05 Punit Agrawal [this message]
2021-09-09 8:05 ` [PATCH 1/2] rteval: osinfo.py: Fix RT kernel detection Punit Agrawal
2021-09-10 16:30 ` John Kacur
2021-09-09 8:05 ` [PATCH 2/2] rteval: services.py: Fix incorrect detection of container environment Punit Agrawal
2021-09-12 14:59 ` John Kacur
2021-09-13 7:47 ` Punit Agrawal
2021-09-13 8:06 ` [PATCH v2] " Punit Agrawal
2021-09-13 13:33 ` 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=20210909080547.1331581-1-punitagrawal@gmail.com \
--to=punitagrawal@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=punit1.agrawal@toshiba.co.jp \
/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