linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: Chris White <chwhite@redhat.com>, Clark Williams <williams@redhat.com>
Subject: [PATCH 7/7] tuna: Change default profile filename to cpuset-profile.yaml
Date: Thu, 16 Jul 2026 13:45:50 -0400	[thread overview]
Message-ID: <20260716174554.126145-8-jkacur@redhat.com> (raw)
In-Reply-To: <20260716174554.126145-1-jkacur@redhat.com>

The default filename for cpuset save/apply operations has been changed
from tuna-profile.yaml to cpuset-profile.yaml. This better reflects the
specific content of the profile file, which contains only cpuset
configuration data.

This change affects:
- tuna cpuset save (default output: cpuset-profile.yaml)
- tuna cpuset apply (default input: cpuset-profile.yaml)

All test cases explicitly specify filenames and are unaffected by this
change.

Assisted-by: Claude:claude-sonnet-4-5
Signed-off-by: John Kacur <jkacur@redhat.com>
---
 tuna-cmd.py | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/tuna-cmd.py b/tuna-cmd.py
index 3d4414d93d0e..5436f68c5029 100755
--- a/tuna-cmd.py
+++ b/tuna-cmd.py
@@ -324,13 +324,13 @@ def gen_parser():
 
     # cpuset save
     cpuset_save = cpuset_subparser.add_parser('save', description='Save cpuset configuration to YAML profile', help='Save cpuset configuration')
-    cpuset_save.add_argument('filename', nargs='?', default='tuna-profile.yaml',
-                             help='Output YAML file (default: tuna-profile.yaml)')
+    cpuset_save.add_argument('filename', nargs='?', default='cpuset-profile.yaml',
+                             help='Output YAML file (default: cpuset-profile.yaml)')
 
     # cpuset apply
     cpuset_apply = cpuset_subparser.add_parser('apply', description='Apply cpuset configuration from YAML profile', help='Apply cpuset configuration')
-    cpuset_apply.add_argument('filename', nargs='?', default='tuna-profile.yaml',
-                              help='Input YAML file (default: tuna-profile.yaml)')
+    cpuset_apply.add_argument('filename', nargs='?', default='cpuset-profile.yaml',
+                              help='Input YAML file (default: cpuset-profile.yaml)')
     cpuset_apply.add_argument('-v', '--verbose', action='store_true',
                               help='Print detailed progress messages')
 
-- 
2.55.0


      parent reply	other threads:[~2026-07-16 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 17:45 [PATCH 0/7] tuna: Add cpuset save/apply functionality John Kacur
2026-07-16 17:45 ` [PATCH 1/7] tuna: Add --show-system flag to filter systemd cpusets John Kacur
2026-07-16 17:45 ` [PATCH 2/7] tuna: Add cpuset save/apply functionality John Kacur
2026-07-16 17:45 ` [PATCH 3/7] tuna: Add comprehensive tests for " John Kacur
2026-07-16 17:45 ` [PATCH 4/7] tuna: Remove obsolete apply command functionality John Kacur
2026-07-16 17:45 ` [PATCH 5/7] tuna: Simplify GUI to monitoring-only functionality John Kacur
2026-07-16 17:45 ` [PATCH 6/7] tuna: Change housekeeping cpuset default to partition=member John Kacur
2026-07-16 17:45 ` John Kacur [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=20260716174554.126145-8-jkacur@redhat.com \
    --to=jkacur@redhat.com \
    --cc=chwhite@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).