On 20/01/21 18:53, Greg KH wrote:
On Mon, Jan 18, 2021 at 09:42:57AM +0800, zhenwei pi wrote:
Hi, Greg
What's the next step I should take?
I need some reviews by the people who will be doing the qemu portion of
this, or someone else, please.
QEMU bits are already part of the last release, s
On 1/21/21 1:53 AM, Greg KH wrote:
X-Gm-Spam: 0
X-Gm-Phishy: 0
On Mon, Jan 18, 2021 at 09:42:57AM +0800, zhenwei pi wrote:
Hi, Greg
What's the next step I should take?
I need some reviews by the people who will be doing the qemu portion of
this, or someone else, please.
thanks,
greg k-h
On Mon, Jan 18, 2021 at 09:42:57AM +0800, zhenwei pi wrote:
> Hi, Greg
>
> What's the next step I should take?
I need some reviews by the people who will be doing the qemu portion of
this, or someone else, please.
thanks,
greg k-h
Hi, Greg
What's the next step I should take?
On 1/10/21 7:53 PM, zhenwei pi wrote:
v4 -> v5:
Use sysfs_emit to export attribute value.
Only allow subset of capability to set on events.
Add more detailed infomation in document.
v3 -> v4:
Use event sysfs attribute instead of module parameter.
Us
v4 -> v5:
Use sysfs_emit to export attribute value.
Only allow subset of capability to set on events.
Add more detailed infomation in document.
v3 -> v4:
Use event sysfs attribute instead of module parameter.
Use driver dev_groups instead of creating files by sysfs_* API.
v2 -> v3:
Seperate the f
5 matches
Mail list logo
