From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: Samuel Moelius <sam.moelius@trailofbits.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] comedi: comedi_test: avoid AI scan timing overflow
Date: Tue, 9 Jun 2026 12:10:52 +0200 [thread overview]
Message-ID: <2026060919-those-bottom-9e3d@gregkh> (raw)
In-Reply-To: <81522481-40d9-45da-84e2-216fd002e3b6@mev.co.uk>
On Tue, Jun 09, 2026 at 09:54:51AM +0100, Ian Abbott wrote:
> On 09/06/2026 06:18, Greg Kroah-Hartman wrote:
> > On Tue, Jun 09, 2026 at 12:14:04AM +0000, Samuel Moelius wrote:
> > > `waveform_ai_cmdtest()` tries to keep timer-driven analog-input scans
> > > representable by limiting `convert_arg` and by making `scan_begin_arg`
> > > at least `convert_arg * scan_end_arg`.
> >
> > Please don't use markdown crud in changelog comments :(
>
> TBF I also use back-quotes for quoting literal programming text. Not
> because they are the same quote marks that markdown uses to quote literal
> text, but because they cannot be confused with C syntax.
But in a changelog, it's not needed. If it's a function, use () at the
end, if it's a variable name, great, just leave it as-is. No need for
`` at all.
thanks,
greg k-h
next prev parent reply other threads:[~2026-06-09 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 0:14 [PATCH] comedi: comedi_test: avoid AI scan timing overflow Samuel Moelius
2026-06-09 5:18 ` Greg Kroah-Hartman
2026-06-09 8:54 ` Ian Abbott
2026-06-09 10:10 ` Greg Kroah-Hartman [this message]
2026-06-09 9:07 ` Ian Abbott
2026-06-09 10:28 ` Ian Abbott
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=2026060919-those-bottom-9e3d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam.moelius@trailofbits.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 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.