public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH] Fix some pt_regs users
Date: Thu, 02 Nov 2006 20:51:28 +0100	[thread overview]
Message-ID: <85odrpiq4f.fsf@orfeo.duckcorp.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

Hi,

There are still some users of pt_regs in the -omap tree. This patch is
fixing only the one I've spotted, so it's possible that there are some
left.


Regards,
Arnaud Patard


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: irq_fixups.patch --]
[-- Type: text/x-patch, Size: 2453 bytes --]

There are still some users of pt_regs in the -omap tree. This patch fixes them.

Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>

---
 drivers/bluetooth/brf6150.c |    5 	2 +	3 -	0 !
 drivers/cbus/retu.c         |    2 	1 +	1 -	0 !
 drivers/cbus/tahvo.c        |    2 	1 +	1 -	0 !
 3 files changed, 4 insertions(+), 5 deletions(-)

Index: linux-omap-2.6/drivers/bluetooth/brf6150.c
===================================================================
--- linux-omap-2.6.orig/drivers/bluetooth/brf6150.c	2006-11-02 20:26:51.000000000 +0100
+++ linux-omap-2.6/drivers/bluetooth/brf6150.c	2006-11-02 20:26:58.000000000 +0100
@@ -569,7 +569,7 @@ static void brf6150_tx_tasklet(unsigned 
 	spin_unlock_irqrestore(&info->lock, flags);
 }
 
-static irqreturn_t brf6150_interrupt(int irq, void *data, struct pt_regs *regs)
+static irqreturn_t brf6150_interrupt(int irq, void *data)
 {
 	struct brf6150_info *info = (struct brf6150_info *)data;
 	u8 iir, msr;
@@ -617,8 +617,7 @@ static irqreturn_t brf6150_interrupt(int
 	return ret;
 }
 
-static irqreturn_t brf6150_wakeup_interrupt(int irq, void *dev_inst,
-					    struct pt_regs *regs)
+static irqreturn_t brf6150_wakeup_interrupt(int irq, void *dev_inst)
 {
 	struct brf6150_info *info = dev_inst;
 	int should_wakeup;
Index: linux-omap-2.6/drivers/cbus/retu.c
===================================================================
--- linux-omap-2.6.orig/drivers/cbus/retu.c	2006-11-02 20:26:51.000000000 +0100
+++ linux-omap-2.6/drivers/cbus/retu.c	2006-11-02 20:26:58.000000000 +0100
@@ -187,7 +187,7 @@ void retu_ack_irq(int id)
 /*
  * RETU interrupt handler. Only schedules the tasklet.
  */
-static irqreturn_t retu_irq_handler(int irq, void *dev_id, struct pt_regs *regs)
+static irqreturn_t retu_irq_handler(int irq, void *dev_id)
 {
 	tasklet_schedule(&retu_tasklet);
 	return IRQ_HANDLED;
Index: linux-omap-2.6/drivers/cbus/tahvo.c
===================================================================
--- linux-omap-2.6.orig/drivers/cbus/tahvo.c	2006-11-02 20:26:51.000000000 +0100
+++ linux-omap-2.6/drivers/cbus/tahvo.c	2006-11-02 20:26:58.000000000 +0100
@@ -182,7 +182,7 @@ void tahvo_set_backlight_level(int level
 /*
  * TAHVO interrupt handler. Only schedules the tasklet.
  */
-static irqreturn_t tahvo_irq_handler(int irq, void *dev_id, struct pt_regs *regs)
+static irqreturn_t tahvo_irq_handler(int irq, void *dev_id)
 {
 	tasklet_schedule(&tahvo_tasklet);
 	return IRQ_HANDLED;

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2006-11-02 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 19:51 Arnaud Patard [this message]
2006-11-09 23:49 ` [PATCH] Fix some pt_regs users Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85odrpiq4f.fsf@orfeo.duckcorp.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=linux-omap-open-source@linux.omap.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox