This is a note to let you know that I've just added the patch titled
mei: mei_hbm_dispatch() returns void
to the 3.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
mei-mei_hbm_dispatch-returns-void.patch
and it can be found in the queue-3.13 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From pebolle@xxxxxxxxxx Thu Feb 6 14:41:08 2014
From: Paul Bolle <pebolle@xxxxxxxxxx>
Date: Thu, 06 Feb 2014 22:53:29 +0100
Subject: mei: mei_hbm_dispatch() returns void
To: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Cc: linux-kernel@xxxxxxxxxxxxxxx, stable@xxxxxxxxxxxxxxx, Tomas Winkler <tomas.winkler@xxxxxxxxx>, Alexander Usyskin <alexander.usyskin@xxxxxxxxx>
Message-ID: <1391723609.1782.2.camel@x220>
From: Paul Bolle <pebolle@xxxxxxxxxx>
Building hbm.o for v3.13.2 triggers a GCC warning:
drivers/misc/mei/hbm.c: In function 'mei_hbm_dispatch':
drivers/misc/mei/hbm.c:596:3: warning: 'return' with a value, in function returning void [enabled by default]
return 0;
^
GCC is correct, obviously. So let's return void instead of zero here.
Signed-off-by: Paul Bolle <pebolle@xxxxxxxxxx>
Cc: Tomas Winkler <tomas.winkler@xxxxxxxxx>
Cc: Alexander Usyskin <alexander.usyskin@xxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
Compile tested only.
drivers/misc/mei/hbm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/misc/mei/hbm.c
+++ b/drivers/misc/mei/hbm.c
@@ -593,7 +593,7 @@ void mei_hbm_dispatch(struct mei_device
*/
if (dev->hbm_state == MEI_HBM_IDLE) {
dev_dbg(&dev->pdev->dev, "hbm: state is idle ignore spurious messages\n");
- return 0;
+ return;
}
switch (mei_msg->hbm_cmd) {
Patches currently in stable-queue which might be from pebolle@xxxxxxxxxx are
queue-3.13/mei-mei_hbm_dispatch-returns-void.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html