From: Randy Dunlap <rdunlap@infradead.org>
To: Jui-Tse Huang <juitse.huang@gmail.com>, linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Johannes Berg <johannes.berg@intel.com>,
Bruno Randolf <br1@einfach.org>,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>
Subject: Re: [PATCH v2] average: Clarify the restrictions
Date: Wed, 1 Jun 2022 08:58:20 -0700 [thread overview]
Message-ID: <97352295-6527-f146-6f55-c4577a80f3a2@infradead.org> (raw)
In-Reply-To: <20220601071907.22070-1-juitse.huang@gmail.com>
On 6/1/22 00:19, Jui-Tse Huang wrote:
> There is several restrictions in the EWMA helper macro that the
> developers should take care of, but the comment does not mentioned yet,
> thus, this patch clarify the restrictions.
>
> Signed-off-by: Jui-Tse Huang <juitse.huang@gmail.com>
> ---
>
> Notes:
> v2: fix spelling and wording (Bruno Randolf)
>
> include/linux/average.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/linux/average.h b/include/linux/average.h
> index a1a8f09631ce..ff0953ba2820 100644
> --- a/include/linux/average.h
> +++ b/include/linux/average.h
> @@ -13,6 +13,9 @@
> * precision and fall-off coefficient determined at compile-time
> * and built into the generated helper funtions.
functions.
> *
> + * This implementation supports up to 30 bits of precition, and only
precision,
> + * the API for fetching non-fractional part is provided for now.
> + *
> * The first argument to the macro is the name that will be used
> * for the struct and helper functions.
> *
--
~Randy
prev parent reply other threads:[~2022-06-01 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 7:19 [PATCH v2] average: Clarify the restrictions Jui-Tse Huang
2022-06-01 15:58 ` Randy Dunlap [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=97352295-6527-f146-6f55-c4577a80f3a2@infradead.org \
--to=rdunlap@infradead.org \
--cc=br1@einfach.org \
--cc=johannes.berg@intel.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=juitse.huang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).