From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH] ARM: OMAP: Remove struct pt_regs from menelaus_irq()
Date: Fri, 27 Oct 2006 18:56:20 +0200 [thread overview]
Message-ID: <45423A34.1010009@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 97 bytes --]
Remove struct pt_regs from menelaus_irq()
Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
[-- Attachment #2: menelaus_warning_patch.txt --]
[-- Type: text/plain, Size: 538 bytes --]
Index: linux-osk/drivers/i2c/chips/menelaus.c
===================================================================
--- linux-osk.orig/drivers/i2c/chips/menelaus.c
+++ linux-osk/drivers/i2c/chips/menelaus.c
@@ -678,7 +678,7 @@ static void menelaus_work(void * _menela
/*
* We cannot use I2C in interrupt context, so we just schedule work.
*/
-static irqreturn_t menelaus_irq(int irq, void *_menelaus, struct pt_regs *regs)
+static irqreturn_t menelaus_irq(int irq, void *_menelaus)
{
struct menelaus_chip *menelaus = _menelaus;
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2006-10-27 16:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45423A34.1010009@gmail.com \
--to=dirk.behme@googlemail.com \
--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