linux-kernel - Re: [RFC PATCH 04/15] drivers/acrn: add the basic framework of acrn char device driver

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: <20190819052619.GC915@kroah.com>
Date:   Mon, 19 Aug 2019 07:26:19 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Zhao, Yakui" <yakui.zhao@...el.com>
Cc:     devel@...verdev.osuosl.org, x86@...nel.org,
        linux-kernel@...r.kernel.org,
        Jason Chen CJ <jason.cj.chen@...el.com>,
        Jack Ren <jack.ren@...el.com>, Liu Shuo <shuo.a.liu@...el.com>,
        Mingqiang Chi <mingqiang.chi@...el.com>
Subject: Re: [RFC PATCH 04/15] drivers/acrn: add the basic framework of acrn
 char device driver

On Mon, Aug 19, 2019 at 12:02:33PM +0800, Zhao, Yakui wrote:
> 
> 
> On 2019年08月16日 15:05, Greg KH wrote:
> > On Fri, Aug 16, 2019 at 10:25:45AM +0800, Zhao Yakui wrote:
> > > ACRN hypervisor service module is the important middle layer that allows
> > > the Linux kernel to communicate with the ACRN hypervisor. It includes
> > > the management of virtualized CPU/memory/device/interrupt for other ACRN
> > > guest. The user-space applications can use the provided ACRN ioctls to
> > > interact with ACRN hypervisor through different hypercalls.
> > > 
> > > Add one basic framework firstly and the following patches will
> > > add the corresponding implementations, which includes the management of
> > > virtualized CPU/memory/interrupt and the emulation of MMIO/IO/PCI access.
> > > The device file of /dev/acrn_hsm can be accessed in user-space to
> > > communicate with ACRN module.
> > > 
> > > Co-developed-by: Jason Chen CJ <jason.cj.chen@...el.com>
> > > Signed-off-by: Jason Chen CJ <jason.cj.chen@...el.com>
> > > Co-developed-by: Jack Ren <jack.ren@...el.com>
> > > Signed-off-by: Jack Ren <jack.ren@...el.com>
> > > Co-developed-by: Mingqiang Chi <mingqiang.chi@...el.com>
> > > Signed-off-by: Mingqiang Chi <mingqiang.chi@...el.com>
> > > Co-developed-by: Liu Shuo <shuo.a.liu@...el.com>
> > > Signed-off-by: Liu Shuo <shuo.a.liu@...el.com>
> > > Signed-off-by: Zhao Yakui <yakui.zhao@...el.com>
> > > ---
> > >   drivers/staging/Kconfig         |   2 +
> > 
> > Also, your subject line for all of these patches are wrong, it is not
> > drivers/acrn :(
> 
> Thanks for the pointing out it.
> 
> It will be fixed.
> 
> > 
> > And you forgot to cc: the staging maintainer :(
> 
> Do you mean that the maintainer of staging subsystem is also added in the
> patch commit log?

Did you not run scripts/get_maintainer.pl on your patches to determine
who to send patches to?  Always do that.

> > As I have said with NUMEROUS Intel patches in the past, I now refuse to
> > take patches from you all WITHOUT having it signed-off-by someone from
> > the Intel "OTC" group (or whatever the Intel Linux group is called these
> > days).  They are a resource you can not ignore, and if you do, you just
> > end up making the rest of the kernel community grumpy by having us do
> > their work for them :(
> > 
> > Please work with them.
> 
> OK. I will work with some peoples in OTC group to prepare the better ACRN
> driver.

Thank you.

greg k-h