All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/sched_rr_get_interval: Convert to docparse
Date: Thu, 4 Jan 2024 16:29:20 +0100	[thread overview]
Message-ID: <20240104152920.GA1176214@pevik> (raw)
In-Reply-To: <20231215190725.GA67360@pevik>

Hi Cyril,

> Hi Cyril,
...
> I was going to merge, but this is really ugly formatting in html.

> If the dates and authors are important, could this comment be inside normal
> comments (e.g. info is in the sources, but not in docparse doc)? Because we have
> that info in docs as linux-git tags.

> Or, if this is not important, could we use just:

> /*\
>  * [Description]
> ....
>  * It is also a regression test for:
I'm sorry, also I miss blank line before list. I need to write check for that.
>  * * 975e155ed8732 ("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in milliseconds")
>  * * c7fcb99877f9f ("sched/rt: Fix sysctl_sched_rr_timeslice intial value")

But feel free to merge either in list in docparse or original version, but with
commits in plain /* */ (will not be in docparse.

Kind regards,
Petr

>  */

> Also, for me would be instead of year enough just to add also kernel release to the hash.

> Reviewed-by: Petr Vorel <pvorel@suse.cz>

> Kind regards,
> Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-04 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 13:27 [LTP] [PATCH] syscalls/sched_rr_get_interval: Convert to docparse Cyril Hrubis
2023-12-08 15:21 ` Cyril Hrubis
2023-12-11 21:02 ` Avinesh Kumar
2023-12-15 19:07 ` Petr Vorel
2024-01-04 15:29   ` Petr Vorel [this message]
2024-01-10 11:29   ` Cyril Hrubis

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=20240104152920.GA1176214@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.