[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190816070559.GB1368@kroah.com>
Date: Fri, 16 Aug 2019 09:05:59 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Zhao Yakui <yakui.zhao@...el.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
devel@...verdev.osuosl.org,
Mingqiang Chi <mingqiang.chi@...el.com>,
Jack Ren <jack.ren@...el.com>,
Jason Chen CJ <jason.cj.chen@...el.com>,
Liu Shuo <shuo.a.liu@...el.com>
Subject: Re: [RFC PATCH 04/15] drivers/acrn: add the basic framework of acrn
char device driver
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 :(
And you forgot to cc: the staging maintainer :(
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.
greg k-h
Powered by blists - more mailing lists