linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
	linux@armlinux.org.uk, kgene@kernel.org, javier@osg.samsung.com,
	linux.amoon@gmail.com, m.szyprowski@samsung.com,
	treding@nvidia.com, b.zolnierkie@samsung.com
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: exynos_defconfig add CONFIG_EXYNOS_IOMMU in not set mode
Date: Thu, 09 Jun 2016 07:04:06 +0200	[thread overview]
Message-ID: <5758F8C6.2090700@samsung.com> (raw)
In-Reply-To: <1465406523-7075-1-git-send-email-shuahkh@osg.samsung.com>

On 06/08/2016 07:22 PM, Shuah Khan wrote:
> Add CONFIG_EXYNOS_IOMMU in not set mode to make it easier to enable it.

Hmmm... How does it make it easier? Enabling such item is just adding
new line, so what is the problem solved here?

Anyway the line will disappear on first savedefconfig (because it should
not be there...) so there is really no point of it.

Best regards,
Krzysztof

> 
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> ---
>  arch/arm/configs/exynos_defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
> index daf9762..16c2957 100644
> --- a/arch/arm/configs/exynos_defconfig
> +++ b/arch/arm/configs/exynos_defconfig
> @@ -218,6 +218,7 @@ CONFIG_CROS_EC_CHARDEV=y
>  CONFIG_COMMON_CLK_MAX77686=y
>  CONFIG_COMMON_CLK_MAX77802=y
>  CONFIG_COMMON_CLK_S2MPS11=y
> +# CONFIG_EXYNOS_IOMMU is not set
>  CONFIG_EXTCON=y
>  CONFIG_EXTCON_MAX14577=y
>  CONFIG_EXTCON_MAX77693=y

      reply	other threads:[~2016-06-09  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 17:22 [PATCH] ARM: exynos_defconfig add CONFIG_EXYNOS_IOMMU in not set mode Shuah Khan
2016-06-09  5:04 ` Krzysztof Kozlowski [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=5758F8C6.2090700@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=javier@osg.samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=shuahkh@osg.samsung.com \
    --cc=treding@nvidia.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).