[PATCH] staging:xgifb:remove unused code

The variable data is assigned but never used in rest code. Signed-off-by: Ding Xiang --- drivers/staging/xgifb/vb_setmode.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging/xgifb/vb_setmode.c index 50c8ea4..71bb9ca 100644 --- a/drivers/sta

Re: [PATCH V2 resend] libata:fix kernel panic when hotplug

Hi,All Hello, On Mon, Jun 20, 2016 at 06:46:55PM -0700, Dan Williams wrote: On Mon, Jun 20, 2016 at 6:22 PM, Martin K. Petersen wrote: "Tejun" == Tejun Heo writes: In fact,we don't need libata to deal with hotplug in sas environment. So we can't run ata hotplug task when ata port is sas ho

[PATCH V2 resend] libata:fix kernel panic when hotplug

In normal condition,if we use sas protocol and hotplug a sata disk on a port,the sas driver will send event "PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed". But if a sata disk is run io and unplug it,then plug a new sata disk,this operation may cause a kernel panic like this: [ 2366.

[PATCH V2] libata:fix kernel panic when hotplug

From: Ding Xiang In normal condition,if we use sas protocol and hotplug a sata disk on a port,the sas driver will send event "PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed". But if a sata disk is run io and unplug it,then plug a new sata disk,this operation may cause a kernel panic

[PATCH resend] libata:fix kernel panic when hotplug

From: Miao Xie In normal condition,if we use sas protocol and hotplug a sata disk on a port, the sas driver will send event "PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed". But if a sata disk is run io and unplug it,then plug a new sata disk,this operation may cause a kernel panic

[PATCH] libata:fix kernel panic when hotplug

In normal condition,if we use sas protocol and hotplug a sata disk on a port, the sas driver will send event "PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed". But if a sata disk is run io and unplug it,then plug a new sata disk,this operation may cause a kernel panic like this: [ 236

Very Confidential Finance Letter:

Hello I am Dingxiang Wong, A staff Member of Maybank Malaysia investment committee and I'm contacting you for a business proposal to transfer $7.3 million to you for investment partnership in your country, this fund belongs to our business partner who has been presume dead in the Mi

[PATCH resend] [dm]fix NULL pointer when create dm device

In some conditions(such as umount fs failed),origin path or origin bdev or both of the two is same as cow's.If this happens, origin dev will be freed when get cow dev in function "dm_get_device" , then "s->origin->dev" which used by "dm_exception_store_set_chunk_size" will be a NULL pointer. He

[PATCH] [dm]fix NULL pointer in dm_exception_store_create() when create dm device

In some conditions(such as umount fs failed),origin path or origin bdev or both of the two is same as cow's.If this happens, origin dev will be freed when get cow dev in function "dm_get_device" , then "s->origin->dev" which used by "dm_exception_store_create" will be a NULL pointer. Signed-off