Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: lJybmMA+phi2oLLNFz9S82RUX+hRcTuWy8/vroKGkqVvE+rTOTMg25gUJgwwePhDJutxmPsZNo
 oN0hMerGaK1pdsCbrpl1E7gRrf95ss7EZVP4WwlvGV8TSuNSbcnIBkV7DSy1kr2NuCGTDmpf2l
 02C3JPswbbMHDZTpR8BE6wmydhgGPUm2M1IxUY3ZJueUpGe6iKwfQ6cCxEDA/5fB8G5D6eELCp
 CJ5rMPPfW3KSXznOGi5AmQCAOUD4ZUj4z1rMLkYNZou2/MNvO9SbbV2WXcjP9zNYvVw9Yz7JuE
 7xE=
From:   Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To:     Jens Axboe <axboe@kernel.dk>
CC:     kernel test robot <lkp@intel.com>, "Jan, Kara," <jack@suse.cz>,
        "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Ming Lei <ming.lei@redhat.com>,
        Bart Van Assche <bvanassche@acm.org>
Subject: Re: kernel/trace/blktrace.c:347:12: sparse: sparse: incorrect type in
 assignment (different address spaces)
Thread-Topic: kernel/trace/blktrace.c:347:12: sparse: sparse: incorrect type
 in assignment (different address spaces)
Thread-Index: AQHWOZq0JeGPDjwwNk2lvn18OjkZKw==
Date:   Wed, 3 Jun 2020 22:34:34 +0000
Message-ID: <BYAPR04MB496578B5C8F42E1639F56D8A86880@BYAPR04MB4965.namprd04.prod.outlook.com>
References: <202006031903.CiDVFCgm%lkp@intel.com>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dcad22f8-9cf4-4957-1a15-08d8080e4a82
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2020 22:34:34.3531
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: D7y8wys5AsxKp2eP3MdiyMRKWUlUVYpSBuloAxZ70AUILM7zXbJar7EIDIBDtceQMi0113eZm3Pfjl6yfzVlawE+UcAUma7bXZ0ivkVSdOs=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR04MB4792
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Jens,=0A=
=0A=
On 6/3/20 4:32 AM, kernel test robot wrote:=0A=
> tree:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git  =
master=0A=
> head:   d6f9469a03d832dcd17041ed67774ffb5f3e73b3=0A=
> commit: c780e86dd48ef6467a1146cf7d0fe1e05a635039 blktrace: Protect q->blk=
_trace with RCU=0A=
> date:   3 months ago=0A=
> config: arc-randconfig-s031-20200603 (attached as .config)=0A=
> compiler: arc-elf-gcc (GCC) 9.3.0=0A=
> reproduce:=0A=
>          # apt-get install sparse=0A=
>          # sparse version: v0.6.1-244-g0ee050a8-dirty=0A=
>          git checkout c780e86dd48ef6467a1146cf7d0fe1e05a635039=0A=
>          # save the attached .config to linux build tree=0A=
>          make W=3D1 C=3D1 ARCH=3Darc CF=3D'-fdiagnostic-prefix -D__CHECK_=
ENDIAN__'=0A=
> =0A=
> If you fix the issue, kindly add following tag as appropriate=0A=
> Reported-by: kernel test robot<lkp@intel.com>=0A=
=0A=
I think Jan has sent the patch to fix the rcu and I've sent out the =0A=
series to fix the rest of the issues.=0A=
=0A=
Can you please let me know how can we proceed with the series so that=0A=
we can stop these emails ?=0A=