From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: mm-commits@vger.kernel.org, davidgow@google.com,
brendanhiggins@google.com, arnd@arndb.de,
geert+renesas@glider.be, akpm@linux-foundation.org
Subject: Re: + lib-add-dhrystone-benchmark-test.patch added to mm-nonmm-unstable branch
Date: Mon, 19 Dec 2022 08:59:46 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2212190857310.137329@ramsan.of.borg> (raw)
In-Reply-To: <20221216224923.58770C433D2@smtp.kernel.org>
Hi Andrew,
On Fri, 16 Dec 2022, Andrew Morton wrote:
> The patch titled
> Subject: lib: add Dhrystone benchmark test
> has been added to the -mm mm-nonmm-unstable branch. Its filename is
> lib-add-dhrystone-benchmark-test.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/lib-add-dhrystone-benchmark-test.patch
>
> This patch will later appear in the mm-nonmm-unstable branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
>
> The -mm tree is included into linux-next via the mm-everything
> branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> and is updated there every 2-3 working days
>
> ------------------------------------------------------
Can you please squash the following small fix?
(Obviously I'm still not used to using a newer gcc than the good
old 4.1, which would have warned about this for sure ;-)
Thanks!
From f03a6abd766c685741dccc59157f4d1addee7ed4 Mon Sep 17 00:00:00 2001
Message-Id: <f03a6abd766c685741dccc59157f4d1addee7ed4.1671436679.git.geert+renesas@glider.be>
From: Geert Uytterhoeven <geert+renesas@glider.be>
Date: Sun, 18 Dec 2022 10:51:59 +0100
Subject: [PATCH] squash! lib: Add Dhrystone benchmark test
v2:
- Fix uninitialized use of ret, as reported by kernel test robot
<lkp@intel.com>.
---
lib/dhry_run.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/dhry_run.c b/lib/dhry_run.c
index 31a1d442e4a0fc19..f9d33efa6d090604 100644
--- a/lib/dhry_run.c
+++ b/lib/dhry_run.c
@@ -69,7 +69,7 @@ static int dhry_run_set(const char *val, const struct kernel_param *kp)
if (dhry_run && system_state == SYSTEM_RUNNING)
dhry_benchmark();
- return ret;
+ return 0;
}
static int __init dhry_init(void)
--
2.25.1
parent reply other threads:[~2022-12-19 7:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221216224923.58770C433D2@smtp.kernel.org>]
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=alpine.DEB.2.22.394.2212190857310.137329@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®