From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: arnd@arndb.de, nsekhar@ti.com, olof@lixom.net, t-kristo@ti.com,
catalin.marinas@arm.com, will@kernel.org, s-anna@ti.com,
hch@lst.de, bjorn.andersson@linaro.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 linux-next 1/4] arm: configs: omap2plus_defconfig: Change CONFIG_REMOTEPROC from m to y
Date: Mon, 23 Sep 2019 10:56:53 -0700 [thread overview]
Message-ID: <20190923175653.GZ5610@atomide.com> (raw)
In-Reply-To: <20190920075946.13282-2-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [190920 08:00]:
> Commit 6334150e9a36 ("remoteproc: don't allow modular build")
> changes CONFIG_REMOTEPROC to a boolean from a tristate config
> option which inhibits all defconfigs marking CONFIG_REMOTEPROC as
> a module in compiling the remoteproc and dependent config options.
>
> So fix the omap2plus_defconfig to have CONFIG_REMOTEPROC built in.
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2019-09-23 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 7:59 [PATCH v2 linux-next 0/4] arm/arm64: configs: Convert all CONFIG_REMOTEPROC instances to y Keerthy
2019-09-20 7:59 ` [PATCH v2 linux-next 1/4] arm: configs: omap2plus_defconfig: Change CONFIG_REMOTEPROC from m " Keerthy
2019-09-23 17:56 ` Tony Lindgren [this message]
2019-09-20 7:59 ` [PATCH v2 linux-next 2/4] arm: configs: davinci_all_defconfig: " Keerthy
2019-09-30 15:09 ` Sekhar Nori
2019-09-20 7:59 ` [PATCH v2 linux-next 3/4] arm: configs: multi_v7_defconfig: " Keerthy
2019-09-20 7:59 ` [PATCH v2 linux-next 4/4] arm64: configs: defconfig: " Keerthy
2019-09-30 13:48 ` Will Deacon
2019-09-30 18:46 ` Olof Johansson
2019-09-30 23:10 ` keerthy
2019-09-25 17:05 ` [PATCH v2 linux-next 0/4] arm/arm64: configs: Convert all CONFIG_REMOTEPROC instances " Christoph Hellwig
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=20190923175653.GZ5610@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=hch@lst.de \
--cc=j-keerthy@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=olof@lixom.net \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).