From: Shuah Khan <skhan@linuxfoundation.org>
To: Vitor Massaru Iha <vitor@massaru.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Brendan Higgins <brendanhiggins@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: build warnings after merge of the kunit-next tree
Date: Thu, 15 Oct 2020 12:01:27 -0600 [thread overview]
Message-ID: <2759fa81-630e-6395-b8e1-c743fb533700@linuxfoundation.org> (raw)
In-Reply-To: <CADQ6JjX0tg51M0FsD+DmAaDcnWB0wrihj4WCq_z6En=tzL=wcg@mail.gmail.com>
On 10/15/20 4:43 AM, Vitor Massaru Iha wrote:
> Hi Stephen,
>
> On Thu, Oct 15, 2020 at 2:31 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi all,
>>
>> After merging the kunit-next tree, today's linux-next build (x86_64
>> allmodconfig) produced this warning:
>>
>> lib/bitfield_kunit.c: In function 'test_bitfields_compile':
>> lib/bitfield_kunit.c:136:21: warning: unsigned conversion from 'int' to 'u16' {aka 'short unsigned int'} changes value from '393216' to '0' [-Woverflow]
>> 136 | u16_encode_bits(0, 0x60000);
>> | ^~~~~~~
>> At top level:
>> lib/bitfield_kunit.c:129:20: warning: 'test_bitfields_compile' defined but not used [-Wunused-function]
>> 129 | static void __init test_bitfields_compile(struct kunit *context)
>> | ^~~~~~~~~~~~~~~~~~~~~~
>>
>> Introduced by commit
>>
>> d2585f5164c2 ("lib: kunit: add bitfield test conversion to KUnit")
>
> I saw the problem, I will send the patch.
>
Please send the fix in as soon as possible. I will go ahead and send the
pull request and will apply the fix in rc2.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-10-15 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 5:30 linux-next: build warnings after merge of the kunit-next tree Stephen Rothwell
2020-10-15 10:43 ` Vitor Massaru Iha
2020-10-15 18:01 ` Shuah Khan [this message]
2020-10-15 18:10 ` Vitor Massaru Iha
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 5:18 Stephen Rothwell
2023-05-30 7:59 ` David Gow
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=2759fa81-630e-6395-b8e1-c743fb533700@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brendanhiggins@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vitor@massaru.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