From: Lokesh Vutla <lokeshvutla@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>
Cc: Sekhar Nori <nsekhar@ti.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Sean Young <sean@mess.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: omap2: set CONFIG_LIRC=y in defconfig
Date: Tue, 27 Feb 2018 11:22:30 +0530 [thread overview]
Message-ID: <6f0e6593-27c3-2df4-b0ef-f3d3e77c81de@ti.com> (raw)
In-Reply-To: <20180226204105.2858838-1-arnd@arndb.de>
On Tuesday 27 February 2018 02:10 AM, Arnd Bergmann wrote:
> The CONFIG_LIRC symbol has changed from 'tristate' to 'bool, so we now
> get a warning for omap2plus_defconfig:
>
> arch/arm/configs/omap2plus_defconfig:322:warning: symbol value 'm' invalid for LIRC
>
> This changes the file to mark the symbol as built-in to get rid of the
> warning.
>
> Fixes: a60d64b15c20 ("media: lirc: lirc interface should not be a raw decoder")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Thank and regards,
Lokesh
> ---
> arch/arm/configs/omap2plus_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/configs/omap2plus_defconfig b/arch/arm/configs/omap2plus_defconfig
> index 2f145c4af93a..92674f247a12 100644
> --- a/arch/arm/configs/omap2plus_defconfig
> +++ b/arch/arm/configs/omap2plus_defconfig
> @@ -319,7 +319,7 @@ CONFIG_MEDIA_CAMERA_SUPPORT=y
> CONFIG_RC_CORE=m
> CONFIG_MEDIA_CONTROLLER=y
> CONFIG_VIDEO_V4L2_SUBDEV_API=y
> -CONFIG_LIRC=m
> +CONFIG_LIRC=y
> CONFIG_RC_DEVICES=y
> CONFIG_IR_RX51=m
> CONFIG_V4L_PLATFORM_DRIVERS=y
>
prev parent reply other threads:[~2018-02-27 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 20:40 Arnd Bergmann
2018-02-26 21:25 ` Tony Lindgren
2018-02-27 5:52 ` Lokesh Vutla [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=6f0e6593-27c3-2df4-b0ef-f3d3e77c81de@ti.com \
--to=lokeshvutla@ti.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=sean@mess.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®