From: Andrew Morton <akpm@linux-foundation.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lib: make a test module with get_count_order/long
Date: Mon, 1 Jun 2020 18:02:51 -0700 [thread overview]
Message-ID: <20200601180251.3f905a6e6eea1debc8771479@linux-foundation.org> (raw)
In-Reply-To: <20200531124709.c7o7pw7o2rfv4klc@master>
On Sun, 31 May 2020 12:47:09 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:
> On Sun, May 31, 2020 at 12:56:29AM +0300, Andy Shevchenko wrote:
> >On Sun, May 31, 2020 at 12:23 AM Wei Yang <richard.weiyang@gmail.com> wrote:
> >> On Sat, May 30, 2020 at 01:25:31PM +0300, Andy Shevchenko wrote:
> >> >On Sat, May 30, 2020 at 12:43:28AM +0000, Wei Yang wrote:
> >> >> A test module to make sure get_count_order/long returns the correct result.
> >> >
> >> >> lib/Kconfig.debug | 13 ++++++
> >> >> lib/Makefile | 2 +
> >> >> lib/test_getorder.c | 64 ++++++++++++++++++++++++++++++
> >> >
> >> >I didn't get why it's not a part of test_bitops?
> >> >
> >>
> >> I see the document of test_bitops says it does exercise on clear_bit and
> >> set_bit. So not sure it is proper to put them together.
> >
> >It's not a problem to amend a documentation as well :-)
> >
>
> Sure. I am fine with this.
>
> Andrew, do you expect me to merge it into test_bitops.c?
>
Yes please.
prev parent reply other threads:[~2020-06-02 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 0:43 Wei Yang
2020-05-30 10:25 ` Andy Shevchenko
2020-05-30 21:19 ` Wei Yang
2020-05-30 21:56 ` Andy Shevchenko
2020-05-31 12:47 ` Wei Yang
2020-06-02 1:02 ` Andrew Morton [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=20200601180251.3f905a6e6eea1debc8771479@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weiyang@gmail.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
all inboxes | Powered by JetHome®