Staging: vme: Pull common VME interrupt handling into core code

[mirror_ubuntu-zesty-kernel.git] / drivers / staging / vme / vme_api.txt

diff --git a/drivers/staging/vme/vme_api.txt b/drivers/staging/vme/vme_api.txt
index 591eba5c903640ff8d07561ae7f305054d50583e..36b7a3c8421f4adfaaafd61f0e0c7704f46556ae 100644 (file)
--- a/drivers/staging/vme/vme_api.txt
+++ b/drivers/staging/vme/vme_api.txt
@@ -290,10 +290,10 @@ status ID combination. Any given combination can only be assigned a single
 callback function. A void pointer parameter is provided, the value of which is
 passed to the callback function, the use of this pointer is user undefined:
 
-       int vme_request_irq(struct device *dev, int level, int statid,
+       int vme_irq_request(struct device *dev, int level, int statid,
                void (*callback)(int, int, void *), void *priv);
 
-       void vme_free_irq(struct device *dev, int level, int statid);
+       void vme_irq_free(struct device *dev, int level, int statid);
 
 The callback parameters are as follows. Care must be taken in writing a callback
 function, callback functions run in interrupt context:
@@ -307,7 +307,7 @@ Interrupt Generation
 The following function can be used to generate a VME interrupt at a given VME
 level and VME status ID:
 
-       int vme_generate_irq(struct device *dev, int level, int statid);
+       int vme_irq_generate(struct device *dev, int level, int statid);
 
 
 Location monitors