From: tip-bot for Thierry Reding <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
hpa@zytor.com, mingo@kernel.org, peterz@infradead.org,
treding@nvidia.com, tglx@linutronix.de
Subject: [tip:sched/core] sched/wait: Fix build breakage
Date: Wed, 23 Oct 2013 05:48:31 -0700 [thread overview]
Message-ID: <tip-92ec11809565cf6429c75204e99e0f583b5c9d7c@git.kernel.org> (raw)
In-Reply-To: <1382528455-29911-1-git-send-email-treding@nvidia.com>
Commit-ID: 92ec11809565cf6429c75204e99e0f583b5c9d7c
Gitweb: http://git.kernel.org/tip/92ec11809565cf6429c75204e99e0f583b5c9d7c
Author: Thierry Reding <thierry.reding@gmail.com>
AuthorDate: Wed, 23 Oct 2013 13:40:55 +0200
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 23 Oct 2013 14:44:10 +0200
sched/wait: Fix build breakage
The wait_event_interruptible_lock_irq() macro is missing a
semi-colon which causes a build failure in the i915 DRM driver.
Signed-off-by: Thierry Reding <treding@nvidia.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1382528455-29911-1-git-send-email-treding@nvidia.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
include/linux/wait.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/wait.h b/include/linux/wait.h
index ec099b0..3b23afa 100644
--- a/include/linux/wait.h
+++ b/include/linux/wait.h
@@ -732,7 +732,7 @@ do { \
int __ret = 0; \
if (!(condition)) \
__ret = __wait_event_interruptible_lock_irq(wq, \
- condition, lock,) \
+ condition, lock,); \
__ret; \
})
prev parent reply other threads:[~2013-10-23 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 11:40 [PATCH] " Thierry Reding
2013-10-23 12:48 ` tip-bot for Thierry Reding [this message]
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=tip-92ec11809565cf6429c75204e99e0f583b5c9d7c@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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
Powered by JetHome