From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Priit Laes <plaes@plaes.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: csr: Replace wakelocks with wakeup interface
Date: Mon, 22 Oct 2012 14:50:00 -0700 [thread overview]
Message-ID: <20121022215000.GA10698@kroah.com> (raw)
In-Reply-To: <1349287950-7278-1-git-send-email-plaes@plaes.org>
On Wed, Oct 03, 2012 at 09:12:30PM +0300, Priit Laes wrote:
> Wakelocks are an Android-specific API that never made into mainline.
> Eventually power management wakeup interface appeared, therefore use
> this interface instead.
>
> Signed-off-by: Priit Laes <plaes@plaes.org>
> ---
> drivers/staging/csr/drv.c | 8 ++++----
> drivers/staging/csr/sdio_mmc.c | 23 +++++++----------------
> drivers/staging/csr/sme_sys.c | 18 +++++++++---------
> drivers/staging/csr/unifi_priv.h | 8 --------
> 4 files changed, 20 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/staging/csr/drv.c b/drivers/staging/csr/drv.c
> index 2497580..262705a 100644
> --- a/drivers/staging/csr/drv.c
> +++ b/drivers/staging/csr/drv.c
> @@ -67,6 +67,8 @@ int bh_priority = -1;
> int log_hip_signals = 0;
> #endif
>
> +extern struct wakeup_source unifi_sdio_wakeup_source;
You obviously didn't run scripts/checkpatch.pl against this patch, did
you?
Never put an extern in a .c file, put this in a .h file so that all .c
files can access it properly.
Care to fix this up and resend?
thanks,
greg k-h
prev parent reply other threads:[~2012-10-22 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 17:14 [PATCH] staging: csr: Replace wakelock code with wakeup sources Priit Laes
2012-10-03 17:22 ` Greg Kroah-Hartman
2012-10-03 18:12 ` [PATCH v2] staging: csr: Replace wakelocks with wakeup interface Priit Laes
2012-10-22 21:50 ` Greg Kroah-Hartman [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=20121022215000.GA10698@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plaes@plaes.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
Powered by JetHome