From: SeongJae Park <sj38.park@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 2/3] staging: alarm-dev: Remove unnecessary blank lines
Date: Thu, 14 Nov 2013 21:15:11 +0900 [thread overview]
Message-ID: <1384431312-2685-2-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1384431312-2685-1-git-send-email-sj38.park@gmail.com>
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
drivers/staging/android/alarm-dev.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/android/alarm-dev.c b/drivers/staging/android/alarm-dev.c
index ccf74ee..a3b467b 100644
--- a/drivers/staging/android/alarm-dev.c
+++ b/drivers/staging/android/alarm-dev.c
@@ -72,7 +72,6 @@ static int is_wakeup(enum android_alarm_type type)
type == ANDROID_ALARM_ELAPSED_REALTIME_WAKEUP;
}
-
static void devalarm_start(struct devalarm *alrm, ktime_t exp)
{
if (is_wakeup(alrm->type))
@@ -111,7 +110,6 @@ static void alarm_clear(enum android_alarm_type alarm_type)
}
alarm_enabled &= ~alarm_type_mask;
spin_unlock_irqrestore(&alarm_slock, flags);
-
}
static void alarm_set(enum android_alarm_type alarm_type,
@@ -371,7 +369,6 @@ static void devalarm_triggered(struct devalarm *alarm)
spin_unlock_irqrestore(&alarm_slock, flags);
}
-
static enum hrtimer_restart devalarm_hrthandler(struct hrtimer *hrt)
{
struct devalarm *devalrm = container_of(hrt, struct devalarm, u.hrt);
--
1.7.9.5
next prev parent reply other threads:[~2013-11-14 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 12:15 [PATCH 1/3] staging: alarm-dev: Remove unnecessary parenthesis SeongJae Park
2013-11-14 12:15 ` SeongJae Park [this message]
2013-11-14 12:15 ` [PATCH 3/3] staging: alarm-dev: Seperate functions with one blank line SeongJae Park
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=1384431312-2685-2-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®