Select Git revision
Search by author
- Any Author
- authors
-
autociadmin
autociadmin
-
chenzeyuan
chenzeyuan
-
余良海 yulianghai
-
兰梦
lanmeng
-
冯春林 fengchunlin
-
刘华 liuhua
-
刘壮 liuzhuang
-
刘杨 liuyang
-
刘涛 liutao02
-
刘涛 liutao
-
刘潇航 liuxiaohang
-
刘硕 liushuo
-
刘祖强
liuzuqiang
-
刘福涛 liufutao
-
刘震宇 liuzhenyu
-
唐鲁严
tangluyan
-
夏凯旋
xiakaixuan
-
奚云飞 xiyunfei
-
孙檬
sunmeng
-
季炜 jiwei
- Jan 21, 2015
-
-
Vadim Rozenfeld authored
-
- Jan 12, 2015
-
-
Joseph Hindin authored
-
- Jan 08, 2015
-
-
Joseph Hindin authored
NetKVM: BZ#1142737: Control interrupt handling fix: enabling on init, no disabling in the interrupt handler Signed-off-by:Joseph Hindin <yhindin@rehat.com>
-
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by:
-
- Jan 06, 2015
-
-
Gal Hammer authored
The driver didn't handle the EvtIoStop so the pending write request was not handled during sleep/hibernate.
-
Vadim Rozenfeld authored
-
- Jan 04, 2015
-
-
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
NetKVM: BZ#1159754: Add MSIX resources only if MSIX resurces are already present; test MSIX availability Signed-off-by: -
Vadim Rozenfeld authored
-
- Jan 02, 2015
-
-
Vadim Rozenfeld authored
-
Vadim Rozenfeld authored
-
- Dec 29, 2014
-
-
Gal Hammer authored
A change to the balloon's service display name caused the handler registation to fail.
-
Gal Hammer authored
It was possible that WdfRequestComplete was called on a cancelled request.
-
Gal Hammer authored
The MessageId parameter was used to decide if the interrupt should be handled as a queue notification. The problem was that a value of zero caused skipping setting the interruprt as serviced.
-
Vadim Rozenfeld authored
-
- Dec 27, 2014
-
-
Vadim Rozenfeld authored
-
Vadim Rozenfeld authored
-
- Dec 26, 2014
-
-
Joseph Hindin authored
Signed-off-by:
-
- Dec 23, 2014
-
-
Vadim Rozenfeld authored
-
Vadim Rozenfeld authored
-
- Dec 19, 2014
-
-
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by:
-
- Dec 15, 2014
-
-
Joseph Hindin authored
-
- Dec 14, 2014
-
-
Vadim Rozenfeld authored
-
- Dec 11, 2014
-
-
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by: -
Joseph Hindin authored
Signed-off-by:
-
- Dec 08, 2014
-
-
Vadim Rozenfeld authored
-
- Dec 07, 2014
-
-
Vadim Rozenfeld authored
-
- Dec 01, 2014
-
-
Joseph Hindin authored
Signed-off-by: -
Gal Hammer authored
The balloon's service didn't take any action on SERVICE_CONTROL_SHUTDOWN notification. This caused a BSOD when the verifier was used on the balloon driver because the service didn't exit and kept an open file handle to the driver.
-
Gal Hammer authored
The device's hardward id was too short and because of that Windows didn't load the driver if the device was hot-plugged in a different address.
-
- Nov 30, 2014
-
-
Julius Rus authored
-
Julius Rus authored
-
Julius Rus authored
-
