lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44408f8f-20ac-a558-ece9-d14c7b99ca50@flygoat.com>
Date:   Mon, 28 Mar 2022 11:01:36 +0100
From:   Jiaxun Yang <jiaxun.yang@...goat.com>
To:     Sui Jingfeng <15330273260@....cn>,
        kernel test robot <lkp@...el.com>,
        Maxime Ripard <mripard@...nel.org>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Roland Scheidegger <sroland@...are.com>,
        Zack Rusin <zackr@...are.com>,
        Christian Gmeiner <christian.gmeiner@...il.com>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        Rob Herring <robh+dt@...nel.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Dan Carpenter <error27@...il.com>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Andrey Zhizhikin <andrey.zhizhikin@...ca-geosystems.com>,
        Sam Ravnborg <sam@...nborg.org>,
        "David S . Miller" <davem@...emloft.net>,
        Lucas Stach <l.stach@...gutronix.de>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Ilia Mirkin <imirkin@...m.mit.edu>,
        Qing Zhang <zhangqing@...ngson.cn>,
        suijingfeng <suijingfeng@...ngson.cn>
Cc:     kbuild-all@...ts.01.org, devicetree@...r.kernel.org,
        linux-mips@...r.kernel.org, dri-devel@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v13 5/6] drm/loongson: add drm driver for loongson display
 controller



在 2022/3/28 10:01, Sui Jingfeng 写道:
>
> On 2022/3/28 16:51, kernel test robot wrote:
>> Hi Sui,
[...]
>>
>
> Hi,  my driver will not used on microblaze arch,
>
> what does this warnings means, do i need to fix this?

Hi Jingfeng,

The problem it discovered is general for all archs.

Type of reg_base (MMIO pointer) should be "void __iomem *" instead of 
"void *"
everywhere, including parameter list.

__iomem is the attribute for MMIO.

Thanks.
- Jiaxun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ