From: Wei Yang <richard.weiyang@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch v2] lib: test get_count_order/long in test_bitops.c
Date: Wed, 10 Jun 2020 22:06:13 +0000 [thread overview]
Message-ID: <20200610220613.ets3envsukjstvlu@master> (raw)
In-Reply-To: <CAHp75VdVUNqUsfr19jKHjba8CPTQhbSK+WfTKwZFtCfK0JtRCw@mail.gmail.com>
On Wed, Jun 10, 2020 at 01:17:28PM +0300, Andy Shevchenko wrote:
>On Wed, Jun 10, 2020 at 2:06 AM Wei Yang <richard.weiyang@gmail.com> wrote:
>> On Tue, Jun 09, 2020 at 12:16:49PM +0300, Andy Shevchenko wrote:
>> >On Mon, Jun 08, 2020 at 10:31:12PM +0000, Wei Yang wrote:
>> >> On Fri, Jun 05, 2020 at 05:16:29PM -0700, Andrew Morton wrote:
>> >
>> >...
>> >
>> >> The test on 64bit machine pass. Since I don't have a 32bit machine by hand,
>> >
>> >Out of curiosity what that machine is?
>> >
>>
>> It is a Intel Xeon Gold CPU.
>
>I suppose it's x86 (and not ia64).
>In this case you can always build an i386 configuration and test on a
>32-bit "machine".
>
Yes, you are right. While last time I tried to run a 32bit guest, it took me a
lot of time to setup. If my understanding is correct, to run on a 32bit
machine, we not only need the kernel but a whole 32bit system. This means I
need to re-install a 32bit system. And I found many distro doesn't support
32bit system any more.
Do you have a better way to setup the environment?
>--
>With Best Regards,
>Andy Shevchenko
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2020-06-10 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 22:37 [Patch v2] lib: test get_count_order/long in test_bitops.c Wei Yang
2020-06-03 9:18 ` Andy Shevchenko
2020-06-03 13:29 ` Wei Yang
2020-06-04 11:50 ` Geert Uytterhoeven
2020-06-04 12:28 ` Wei Yang
2020-06-04 12:51 ` Geert Uytterhoeven
2020-06-05 23:06 ` Wei Yang
2020-06-06 0:16 ` Andrew Morton
2020-06-08 22:31 ` Wei Yang
2020-06-09 9:16 ` Andy Shevchenko
2020-06-09 23:02 ` Wei Yang
2020-06-10 10:17 ` Andy Shevchenko
2020-06-10 22:06 ` Wei Yang [this message]
2020-06-11 7:25 ` Andy Shevchenko
2020-06-12 14:28 ` Wei Yang
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=20200610220613.ets3envsukjstvlu@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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