summaryrefslogtreecommitdiff
path: root/include/linux/ipmi_smi.h
diff options
context:
space:
mode:
authorCorey Minyard <cminyard@mvista.com>2014-11-07 16:57:31 +0300
committerCorey Minyard <cminyard@mvista.com>2014-12-12 00:04:11 +0300
commit99ab32f3b5d705be562b8c4d9dca7c1ae3dc2cdf (patch)
tree3577b74fa4a0f45cb9db83bfb0a02eb1d12e5349 /include/linux/ipmi_smi.h
parentb874b985c816c74a9bda04082f18db88dcbc808a (diff)
downloadlinux-99ab32f3b5d705be562b8c4d9dca7c1ae3dc2cdf.tar.xz
ipmi: Remove the now unused priority from SMI sender
Since the queue was moved into the message handler, the priority field is now irrelevant. Signed-off-by: Corey Minyard <cminyard@mvista.com>
Diffstat (limited to 'include/linux/ipmi_smi.h')
-rw-r--r--include/linux/ipmi_smi.h9
1 files changed, 4 insertions, 5 deletions
diff --git a/include/linux/ipmi_smi.h b/include/linux/ipmi_smi.h
index 6131845016d9..0b1e569f5ff5 100644
--- a/include/linux/ipmi_smi.h
+++ b/include/linux/ipmi_smi.h
@@ -98,12 +98,11 @@ struct ipmi_smi_handlers {
operation is not allowed to fail. If an error occurs, it
should report back the error in a received message. It may
do this in the current call context, since no write locks
- are held when this is run. If the priority is > 0, the
- message will go into a high-priority queue and be sent
- first. Otherwise, it goes into a normal-priority queue. */
+ are held when this is run. Message are delivered one at
+ a time by the message handler, a new message will not be
+ delivered until the previous message is returned. */
void (*sender)(void *send_info,
- struct ipmi_smi_msg *msg,
- int priority);
+ struct ipmi_smi_msg *msg);
/* Called by the upper layer to request that we try to get
events from the BMC we are attached to. */