linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: baytrail: Fix compilation warnings when !CONFIG_PM
Date: Fri, 16 Oct 2015 22:54:58 +0200	[thread overview]
Message-ID: <CACRpkdY+OqSG5NfUQTGDru5qTERZ6APP6urNQDMCfMLE8CMAMQ@mail.gmail.com> (raw)
In-Reply-To: <1444747886-70568-2-git-send-email-mika.westerberg@linux.intel.com>

On Tue, Oct 13, 2015 at 4:51 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:

> When CONFIG_PM is not set we get following compilation warnings:
>
>  warning: ‘byt_gpio_runtime_suspend’ defined but not used [-Wunused-function]
>  warning: ‘byt_gpio_runtime_resume’ defined but not used [-Wunused-function]
>
> Fix this by guarding byt_gpio_runtime_suspend()/byt_gpio_runtime_resume()
> with #ifdef CONFIG_PM.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Patch applied.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-10-16 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 14:51 [PATCH 1/2] pinctrl: intel: Fix compilation warning when !CONFIG_PM_SLEEP Mika Westerberg
2015-10-13 14:51 ` [PATCH 2/2] pinctrl: baytrail: Fix compilation warnings when !CONFIG_PM Mika Westerberg
2015-10-16 20:54   ` Linus Walleij [this message]
2015-10-16 20:54 ` [PATCH 1/2] pinctrl: intel: Fix compilation warning when !CONFIG_PM_SLEEP Linus Walleij

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=CACRpkdY+OqSG5NfUQTGDru5qTERZ6APP6urNQDMCfMLE8CMAMQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mika.westerberg@linux.intel.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).