From: Hans de Goede <hdegoede@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] radio-shark: Mark shark_resume_leds() inline to kill compiler warning
Date: Sun, 17 Nov 2013 14:40:29 +0100 [thread overview]
Message-ID: <5288C74D.7070206@redhat.com> (raw)
In-Reply-To: <1382962565-1662-1-git-send-email-geert@linux-m68k.org>
Hi,
On 10/28/2013 01:16 PM, Geert Uytterhoeven wrote:
> If SHARK_USE_LEDS=1, but CONFIG_PM=n:
>
> drivers/media/radio/radio-shark.c:275: warning: ‘shark_resume_leds’ defined but not used
>
> Instead of making the #ifdef logic even more complicated (there are already
> two definitions of shark_resume_leds()), mark shark_resume_leds() inline to
> kill the compiler warning. shark_resume_leds() is small and it has only one
> caller.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> {cris,m68k,parisc,sparc,xtensa}-all{mod,yes}config
>
> drivers/media/radio/radio-shark.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/radio/radio-shark.c b/drivers/media/radio/radio-shark.c
> index b91477212413..050b3bb96fec 100644
> --- a/drivers/media/radio/radio-shark.c
> +++ b/drivers/media/radio/radio-shark.c
> @@ -271,7 +271,7 @@ static void shark_unregister_leds(struct shark_device *shark)
> cancel_work_sync(&shark->led_work);
> }
>
> -static void shark_resume_leds(struct shark_device *shark)
> +static inline void shark_resume_leds(struct shark_device *shark)
> {
> if (test_bit(BLUE_IS_PULSE, &shark->brightness_new))
> set_bit(BLUE_PULSE_LED, &shark->brightness_new);
>
Thanks for the patch. I've added this to my tree for 3.13 .
Regards,
Hans
prev parent reply other threads:[~2013-11-17 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 12:16 [PATCH] [media] radio-shark: Mark shark_resume_leds() inline to kill compiler warning Geert Uytterhoeven
2013-11-17 13:40 ` Hans de Goede [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=5288C74D.7070206@redhat.com \
--to=hdegoede@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).