[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <847fb409-e135-c7b7-bc22-fc2f8952fae3@ti.com>
Date: Fri, 17 Jul 2020 16:43:14 +0300
From: Tero Kristo <t-kristo@...com>
To: Arnd Bergmann <arnd@...db.de>
CC: Faiz Abbas <faiz_abbas@...com>, Sekhar Nori <nsekhar@...com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
DTML <devicetree@...r.kernel.org>,
linux-mmc <linux-mmc@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Will Deacon <will@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Rob Herring <robh+dt@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
ARM-SoC Maintainers <soc@...nel.org>,
Nishanth Menon <nm@...com>
Subject: Re: [PATCH 7/7] arm64: defconfig: Enable AM654x SDHCI controller
On 17/07/2020 16:09, Arnd Bergmann wrote:
> On Fri, Jul 17, 2020 at 1:20 PM Tero Kristo <t-kristo@...com> wrote:
>> On 17/07/2020 11:38, Faiz Abbas wrote:
>>> On 16/07/20 11:58 pm, Arnd Bergmann wrote:
>>>> On Thu, Jul 16, 2020 at 3:25 PM Sekhar Nori <nsekhar@...com> wrote:
>>>> I tend to ignore individual patches to the defconfig file unless
>>>> they are sent to:soc@...nel.org. The best way to get them
>>>> included is to have the platform maintainers pick up the
>>>> changes and send them that way as a separate pull request
>>>> at the same time as sending any DT updates.
>>>>
>>>> The MAINTAINERS file lists Tero and Nishanth as maintainers
>>>> for the platform. If they want, I can apply this one directly, but in
>>>> the future, send it to them.
>>>>
>>>
>>> Thanks for clarifying Arnd. Tero, can you pick this up?
>>
>> Ok, this topic has been bit unclear for me also, but if you say I can
>> pick the patches myself and send a pull request out, I can do that.
>
> Right. To clarify, the soc tree usually has separate branches for dts
> files, soc specific drivers, defconfig files and 32-bit platform code.
>
> When you pick up patches into your tree, please put them into
> branches that fit into those categories. You can group the patches
> into branches with more fine-grained categories if it makes sense
> (e.g. adding a particularly large driver, adding a new dts files for a
> new soc, or cosmetic cleanups across dts files).
>
> If any of the categories only have a couple of patches in them, you
> can decide to forward those as patches to soc@...nel.org, but a
> pull request is always ok as well, even for a one-line patch.
Ok thanks for clarification, Arnd.
Based on that, queuing this up for 5.9 myself, thanks.
Will post pull-request next week for it, there appears to be another K3
SoC related config change pending which I'll pick up also. Just want to
capture -next results for these to see how well they integrate.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
Powered by blists - more mailing lists