linux-kernel - Re: [PATCH V5 1/3] misc/pvpanic: return 0 for empty body registerfunction

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20181219094601.GB11441@kroah.com>
Date:   Wed, 19 Dec 2018 10:46:01 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     peng.hao2@....com.cn
Cc:     arnd@...db.de, andy.shevchenko@...il.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH V5 1/3]  misc/pvpanic: return 0 for empty body
 registerfunction

On Wed, Dec 19, 2018 at 05:03:21PM +0800, peng.hao2@....com.cn wrote:
> >> Return 0 for empty body register function normally.
> >>
> >> Signed-off-by: Peng Hao <peng.hao2@....com.cn>
> >> ---
> >> v4 --> v5 : handle all typo "drvier/driver" in funtion name.
> >>
> >> v3 --> v4 : use pcim* function instead of pci* function.
> >>             handle typo "drvier/driver" in funtion name.
> >>
> >> v2 --> v3 : handle a uninitialized variable in some path.
> >>
> >> v2 --> v1 : arch=sh don't support pci, adjust  CONFIG_PCI macro.
> >>
> >> v1 : QEMU community requires additional PCI devices to simulate PVPANIC devices
> >> so that some architectures can not occupy precious less than 4G of memory
> >> space.
> >
> >Have you also fixed the kbuild issues that keep getting reported?
> >
> 
> yes.  v2--> v1 fixed the first kbuild issue.
>          v2--> v3 fixed the second kbuild issue.
>          v4 -->v5 fixed the last two kbuild issues.

And why did you not list all of this?  Am I supposed to just guess it?
:(