From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bhuna.collabora.co.uk ([46.235.227.227]:35914 "EHLO
        bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752031AbeEOCps (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Mon, 14 May 2018 22:45:48 -0400
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org, jra@google.com,
        tytso@mit.edu, olaf@sgi.com, darrick.wong@oracle.com,
        kernel@lists.collabora.co.uk
Subject: Re: [PATCH 04/15] nls: Split default charset from NLS core
References: <20180509064800.28658-5-krisman@collabora.co.uk>
        <201805092210.rmRjBwsU%fengguang.wu@intel.com>
Date: Mon, 14 May 2018 23:45:41 -0300
In-Reply-To: <201805092210.rmRjBwsU%fengguang.wu@intel.com> (kbuild test
        robot's message of "Wed, 9 May 2018 22:52:45 +0800")
Message-ID: <87po1xfxgq.fsf@collabora.co.uk>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

kbuild test robot <lkp@intel.com> writes:

> sparse warnings: (new ones prefixed by >>)
>
>>> fs/nls/nls_default.c:118:20: sparse: incorrect type in assignment
>>> (different base types) @@ expected unsigned short [unsigned] [short]
>>> [usertype] <noident> @@ got unsigned] [short] [usertype] <noident> @@
>    fs/nls/nls_default.c:118:20:    expected unsigned short [unsigned] [short] [usertype] <noident>
>    fs/nls/nls_default.c:118:20:    got restricted __le16 [usertype] <noident>
>    fs/nls/nls_default.c:121:20: sparse: incorrect type in assignment
> (different base types) @@ expected unsigned short [unsigned] [short]
> [usertype] <noident> @@ got unsigned] [short] [usertype] <noident> @@
>    fs/nls/nls_default.c:121:20:    expected unsigned short [unsigned] [short] [usertype] <noident>
>    fs/nls/nls_default.c:121:20:    got restricted __be16 [usertype] <noident>

[snip.]

This is not caused by my patch, but it is identified because I am moving
code around.  I don't plan to fix it in my patch set at this moment.

-- 
Gabriel Krisman Bertazi