From: Tomas Winkler Date: Tue, 6 Mar 2012 20:34:32 +0000 (+0200) Subject: staging/mei: don't use read buffer for writing X-Git-Tag: firefly_0821_release~3680^2~3347^2~55 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=97d5cb094cd2fb3e646b4a8cbc30445e61d62ef8;p=firefly-linux-kernel-4.4.55.git staging/mei: don't use read buffer for writing In mei_irq_thread_read_bus_message we reused mei_hdr allocated on read buffer to write the stop message. There is no bug associated with this but for code clarity we use write buffer also for message header. Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/staging/mei/interrupt.c b/drivers/staging/mei/interrupt.c index ce14e399adab..e70bc3714c13 100644 --- a/drivers/staging/mei/interrupt.c +++ b/drivers/staging/mei/interrupt.c @@ -652,6 +652,7 @@ static void mei_irq_thread_read_bus_message(struct mei_device *dev, } else { dev->version = version_res->me_max_version; /* send stop message */ + mei_hdr = (struct mei_msg_hdr *)&dev->wr_msg_buf[0]; mei_hdr->host_addr = 0; mei_hdr->me_addr = 0; mei_hdr->length = sizeof(struct hbm_host_stop_request);