From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm64: defconfig: enable SMMUv3 config
Date: Mon, 16 Jan 2017 16:15:36 +0000 [thread overview]
Message-ID: <587CF1A8.8020508@hisilicon.com> (raw)
In-Reply-To: <3026029.1QgHzGBYeh@wuerfel>
Hi Arnd,
On 2017/1/13 16:58, Arnd Bergmann wrote:
> On Friday, January 13, 2017 3:35:54 PM CET Wei Xu wrote:
>> On 2017/1/12 9:47, Catalin Marinas wrote:
>>> On Thu, Jan 12, 2017 at 08:36:12AM +0800, Zhou Wang wrote:
>>>> On 2017/1/9 19:50, Zhou Wang wrote:
>>>>> Signed-off-by: Zhou Wang <wangzhou1@hisilicon.com>
>>>>> ---
>>>>> arch/arm64/configs/defconfig | 1 +
>>>>> 1 file changed, 1 insertion(+)
>>>>>
>>>>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>>>>> index 869dded..3520c50 100644
>>>>> --- a/arch/arm64/configs/defconfig
>>>>> +++ b/arch/arm64/configs/defconfig
>>>>> @@ -440,6 +440,7 @@ CONFIG_PLATFORM_MHU=y
>>>>> CONFIG_BCM2835_MBOX=y
>>>>> CONFIG_HI6220_MBOX=y
>>>>> CONFIG_ARM_SMMU=y
>>>>> +CONFIG_ARM_SMMU_V3=y
>>>>> CONFIG_RASPBERRYPI_POWER=y
>>>>> CONFIG_QCOM_SMEM=y
>>>>> CONFIG_QCOM_SMD=y
>>>>
>>>> I just happened to find there is no SMMUv3 config in arm64 defconfig.
>>>>
>>>> Maybe we should add it in defconfig or I miss something.
>>>
>>
>> Hi Arnd,
>>
>>> It looks fine to me but it's usually the arm-soc guys picking the
>>> defconfig patches.
>>>
>>
>> It is fine to me.
>> Is it OK for me to pick up this or will you directly pick up this?
>> Thanks!
>
> Either way works for me. I usually recommend platform maintainers
> picking up patches and then sending them on to arm at kernel.org,
> as that gets our attention quicker. A patch that gets sent with
> me personally on Cc might get lost in the email.
In this case I will pick up it.
Thanks!
Best Regards,
Wei
>
> Arnd
>
>
> .
>
next prev parent reply other threads:[~2017-01-16 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 11:50 [RFC PATCH] arm64: defconfig: enable SMMUv3 config Zhou Wang
2017-01-12 0:36 ` Zhou Wang
2017-01-12 9:47 ` Catalin Marinas
2017-01-13 15:35 ` Wei Xu
2017-01-13 16:58 ` Arnd Bergmann
2017-01-16 16:15 ` Wei Xu [this message]
2017-01-17 0:56 ` Zhou Wang
2017-01-20 16:57 ` Wei Xu
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=587CF1A8.8020508@hisilicon.com \
--to=xuwei5@hisilicon.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 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).