From: Sebastien Bessiere <sebastien.bessiere@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Sebastien Bessiere <sebastien.bessiere@gmail.com>
Subject: [PATCH] trivial: powerpc: fix typo in ioei_interrupt() description
Date: Fri, 14 Jun 2013 17:57:03 +0200 [thread overview]
Message-ID: <1371225423-3039-1-git-send-email-sebastien.bessiere@gmail.com> (raw)
Signed-off-by: Sebastien Bessiere <sebastien.bessiere@gmail.com>
---
arch/powerpc/platforms/pseries/io_event_irq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/pseries/io_event_irq.c b/arch/powerpc/platforms/pseries/io_event_irq.c
index ef9d9d8..5ea88d1 100644
--- a/arch/powerpc/platforms/pseries/io_event_irq.c
+++ b/arch/powerpc/platforms/pseries/io_event_irq.c
@@ -115,7 +115,7 @@ static struct pseries_io_event * ioei_find_event(struct rtas_error_log *elog)
* by scope or event type alone. For example, Torrent ISR route change
* event is reported with scope 0x00 (Not Applicatable) rather than
* 0x3B (Torrent-hub). It is better to let the clients to identify
- * who owns the the event.
+ * who owns the event.
*/
static irqreturn_t ioei_interrupt(int irq, void *dev_id)
--
1.7.9.5
reply other threads:[~2013-06-14 15:57 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=1371225423-3039-1-git-send-email-sebastien.bessiere@gmail.com \
--to=sebastien.bessiere@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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