From: Arnd Bergmann <arnd@arndb.de>
To: Tero Kristo <t-kristo@ti.com>
Cc: Faiz Abbas <faiz_abbas@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
ARM-SoC Maintainers <soc@kernel.org>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 7/7] arm64: defconfig: Enable AM654x SDHCI controller
Date: Fri, 17 Jul 2020 15:09:26 +0200 [thread overview]
Message-ID: <CAK8P3a3Uc1X9PY6OnxbgEyBVY1=sx1drW7JrGzcPv1KrXaK7aQ@mail.gmail.com> (raw)
In-Reply-To: <933d7132-5d9f-89df-8dec-5d9f6d3e0eee@ti.com>
On Fri, Jul 17, 2020 at 1:20 PM Tero Kristo <t-kristo@ti.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@ti.com> wrote:
> >> I tend to ignore individual patches to the defconfig file unless
> >> they are sent to:soc@kernel.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@kernel.org, but a
pull request is always ok as well, even for a one-line patch.
Arnd
Arnd
next prev parent reply other threads:[~2020-07-17 13:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 12:57 [PATCH 0/7] Add support for SD card in AM654x-evm Faiz Abbas
2020-06-19 12:57 ` [PATCH 1/7] dt-bindings: mmc: sdhci-am654: Add ti,clkbuf-sel binding Faiz Abbas
2020-06-19 12:57 ` [PATCH 2/7] mmc: sdhci_am654: Add flag for PHY calibration Faiz Abbas
2020-06-19 12:57 ` [PATCH 3/7] mmc: sdhci_am654: Add Support for SR2.0 Faiz Abbas
2020-06-19 12:57 ` [PATCH 4/7] mmc: sdhci_am654: Fix conditions for enabling dll Faiz Abbas
2020-06-19 12:57 ` [PATCH 5/7] mmc: sdhci_am654: Update delay chain configuration Faiz Abbas
2020-06-19 12:58 ` [PATCH 6/7] mmc: sdhci_am654: Add support for clkbuf_sel property Faiz Abbas
2020-06-19 12:58 ` [PATCH 7/7] arm64: defconfig: Enable AM654x SDHCI controller Faiz Abbas
2020-07-16 12:19 ` Faiz Abbas
2020-07-16 13:25 ` Sekhar Nori
2020-07-16 18:28 ` Arnd Bergmann
2020-07-17 8:38 ` Faiz Abbas
2020-07-17 11:20 ` Tero Kristo
2020-07-17 13:09 ` Arnd Bergmann [this message]
2020-07-17 13:36 ` Faiz Abbas
2020-07-17 13:43 ` Tero Kristo
2020-07-03 7:27 ` [PATCH 0/7] Add support for SD card in AM654x-evm Faiz Abbas
2020-07-06 14:48 ` Ulf Hansson
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='CAK8P3a3Uc1X9PY6OnxbgEyBVY1=sx1drW7JrGzcPv1KrXaK7aQ@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=adrian.hunter@intel.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=t-kristo@ti.com \
--cc=ulf.hansson@linaro.org \
--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).