From: Andrew Morton <akpm@linux-foundation.org>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org,
Clement Courbet <courbet@google.com>,
Matthew Wilcox <mawilcox@microsoft.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH] lib: test module for find_*_bit() functions
Date: Tue, 14 Nov 2017 15:55:55 -0800 [thread overview]
Message-ID: <20171114155555.a9cb0898e257b0641b82e80b@linux-foundation.org> (raw)
In-Reply-To: <20171114100730.fhqvupfa5oxmutfl@yury-thinkpad>
On Tue, 14 Nov 2017 13:07:30 +0300 Yury Norov <ynorov@caviumnetworks.com> wrote:
> > Yyra, you can grab CONFIG_BENCHMARK_* namespace :-)
>
> There's no CONFIG_BENCHMARK_* namespace actually.
Alexey means you can be the first user of CONFIG_BENCHMARK_*.
> The 'CONFIG_*_BENCHMARK' is
> referenced only 3 times in linux sources - CONFIG_RING_BUFFER_BENCHMARK,
> CONFIG_TRACEPOINT_BENCHMARK and CONFIG_GUP_BENCHMARK, so I simply didn't know
> about it. Some other tests like lib/rbtree_test.c also measure performance and
> use TEST namespace, but if you think it's better, I don't object to change it.
>
> > Another thing:
> >
> > > +
> > > + return 0;
> > > +}
> > > +module_init(find_bit_test);
> > > +
> > > +static void __exit test_find_bit_cleanup(void)
> > > +{
> > > +}
> > > +module_exit(test_find_bit_cleanup);
> >
> > module exit hook is entirely unnecessary as you can return -E from init hook.
> > See lib/test-kstrtox.c
>
> Ack.
>
> I thought to send v3, but the patch is already in next tree, so I'll
> send fix in separated patch. OK?
Either approach is OK.
next prev parent reply other threads:[~2017-11-14 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:07 [PATCH] lib: test module for find_*_bit() functions Yury Norov
2017-11-09 14:33 ` Clement Courbet
2017-11-09 23:15 ` Andrew Morton
2017-11-10 10:45 ` Alexey Dobriyan
2017-11-14 10:07 ` Yury Norov
2017-11-14 23:55 ` Andrew Morton [this message]
2017-11-12 11:33 ` Michael Ellerman
2017-11-14 10:58 ` Yury Norov
2017-11-21 8:38 ` Geert Uytterhoeven
2017-11-24 14:30 ` Yury Norov
2017-11-24 15:46 ` Geert Uytterhoeven
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=20171114155555.a9cb0898e257b0641b82e80b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=courbet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mawilcox@microsoft.com \
--cc=ynorov@caviumnetworks.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