From: "Furkan Çalışkan" <frn1furkan10@gmail.com>
To: "Jürgen Groß" <jgross@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, dfaggioli@suse.com,
gwd@xenproject.org, stewart.hildebrand@amd.com,
jbeulich@suse.com
Subject: Re: [PATCH] xen/sched: fix stale file path comments in common/sched directory
Date: Tue, 26 May 2026 09:26:41 +0300 [thread overview]
Message-ID: <ee6892c3-db90-46f2-b245-b0b377ee8de6@gmail.com> (raw)
In-Reply-To: <1ba4ffba-e9e0-4858-b3b9-d45c950894c3@suse.com>
On 5/26/26 09:18, Jürgen Groß wrote:
> On 25.05.26 12:58, Roger Pau Monné wrote:
>> On Mon, May 25, 2026 at 01:25:38PM +0300, Furkan Caliskan wrote:
>>> Commit 6cb4b01c03 ("xen/sched: move schedulers and cpupool coding to
>>> dedicated directory") moved the scheduler files from xen/common/ to
>>> xen/common/sched and renamed some of them, but did not update the
>>> in-file path comments at the top of each file.
>>>
>>> Update the comments to reflect the current file locations.
>>
>> FWIW, if we have to modify those lines I would just delete them, I
>> don't think they add anything meaningful to the file.
>
> Wanted to write the same. So yes, please drop the lines instead of
> modifying them.
>
>
> Juergen
Thanks for the feedback. I'll send a v2 with the lines dropped.
Furkan Caliskan
next prev parent reply other threads:[~2026-05-26 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 10:25 [PATCH] xen/sched: fix stale file path comments in common/sched directory Furkan Caliskan
2026-05-25 10:58 ` Roger Pau Monné
2026-05-26 6:18 ` Jürgen Groß
2026-05-26 6:26 ` Furkan Çalışkan [this message]
2026-05-26 7:52 ` [PATCH v2] xen/sched: remove " Furkan Caliskan
2026-05-26 10:09 ` Jürgen Groß
2026-05-27 19:51 ` Stewart Hildebrand
2026-05-28 10:17 ` Andrew Cooper
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=ee6892c3-db90-46f2-b245-b0b377ee8de6@gmail.com \
--to=frn1furkan10@gmail.com \
--cc=dfaggioli@suse.com \
--cc=gwd@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=stewart.hildebrand@amd.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.