From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mfd: add #ifdef CONFIG_DEBUG_FS guard for ab8500_debug_resources
Date: Mon, 14 Nov 2011 01:32:03 +0100 [thread overview]
Message-ID: <20111114003203.GK22218@sortiz-mobl> (raw)
In-Reply-To: <1320890178.13074.1.camel@phoenix>
Hi Axel,
On Thu, Nov 10, 2011 at 09:56:18AM +0800, Axel Lin wrote:
> Fix below build warning if CONFIG_DEBUG_FS is disabled.
>
> CC drivers/mfd/ab8500-core.o
> drivers/mfd/ab8500-core.c:623: warning: 'ab8500_debug_resources' defined but not used
>
Thanks for the fix, I applied this one to my for-linus branch.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
Linus Walleij <linus.walleij@stericsson.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mfd: add #ifdef CONFIG_DEBUG_FS guard for ab8500_debug_resources
Date: Mon, 14 Nov 2011 01:32:03 +0100 [thread overview]
Message-ID: <20111114003203.GK22218@sortiz-mobl> (raw)
In-Reply-To: <1320890178.13074.1.camel@phoenix>
Hi Axel,
On Thu, Nov 10, 2011 at 09:56:18AM +0800, Axel Lin wrote:
> Fix below build warning if CONFIG_DEBUG_FS is disabled.
>
> CC drivers/mfd/ab8500-core.o
> drivers/mfd/ab8500-core.c:623: warning: 'ab8500_debug_resources' defined but not used
>
Thanks for the fix, I applied this one to my for-linus branch.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-11-14 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 1:56 [PATCH] mfd: add #ifdef CONFIG_DEBUG_FS guard for ab8500_debug_resources Axel Lin
2011-11-10 1:56 ` Axel Lin
2011-11-10 8:41 ` Linus Walleij
2011-11-10 8:41 ` Linus Walleij
2011-11-14 0:32 ` Samuel Ortiz [this message]
2011-11-14 0:32 ` Samuel Ortiz
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=20111114003203.GK22218@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.