From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 04/11] arm64: dts: sc9836/sc9860: Update coresight bindings for hardware ports
Date: Fri, 28 Sep 2018 12:45:07 +0200 [thread overview]
Message-ID: <CAK8P3a2WWFp5W5-7o-X3joOpSGgnK=s_ZyGev7gsVV0SjN0p0A@mail.gmail.com> (raw)
In-Reply-To: <CAAfSe-swWPgCWN6cZbQxLL6fwaJ1qLXnC_X7A0zeYuHDaZ_A1Q@mail.gmail.com>
On Thu, Sep 27, 2018 at 11:19 AM Chunyan Zhang <zhang.lyra@gmail.com> wrote:
>
> Hi Suzuki,
>
> On 27 September 2018 at 16:51, Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
> > +To: Chunyan Zhang
> >
> > Chunyan Zhang,
> >
> > On 09/12/2018 02:53 PM, Suzuki K Poulose wrote:
> >>
> >> Switch to the new coresight bindings for hw ports
> >>
> >
> > How can we push this patch ? Do you generally send the spreadtrum
> > specific changes to ARM soc folks ? Or would you like me to post
> > this directly to ARM soc folks ?
>
> Yeah, at present sprd dts files generally got merged through arm-soc
> (I've added arm at kernel.org).
Yes, that's fine. Generally, we prefer if you collect patches for your
platform first, and then send them as a pull request or short set
of patches. for inclusion, rather than picking them up from the list.
If this is the only DT patch for spreadtrum in 4.20, I can also just
pick it up with your Ack.
Arnd
next prev parent reply other threads:[~2018-09-28 10:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 13:53 [PATCH v2 00/11] dts: Update coresight device tree bindings Suzuki K Poulose
2018-09-12 13:53 ` [PATCH v2 01/11] coresight: dts: binding: Fix example for TPIU component Suzuki K Poulose
2018-09-26 20:30 ` Rob Herring
2018-09-12 13:53 ` [PATCH v2 02/11] coresight: dts: binding: Update coresight binding examples Suzuki K Poulose
2018-09-12 13:53 ` [PATCH v2 03/11] arm64: dts: hi6220: Update coresight bindings for hardware ports Suzuki K Poulose
2018-09-21 14:06 ` Wei Xu
2018-09-12 13:53 ` [PATCH v2 04/11] arm64: dts: sc9836/sc9860: " Suzuki K Poulose
2018-09-27 8:51 ` Suzuki K Poulose
2018-09-27 9:18 ` Chunyan Zhang
2018-09-28 10:45 ` Arnd Bergmann [this message]
2018-09-28 11:09 ` Chunyan Zhang
2018-09-12 13:53 ` [PATCH v2 05/11] arm64: dts: msm8916: " Suzuki K Poulose
2018-09-27 8:18 ` Suzuki K Poulose
2018-09-30 17:12 ` Andy Gross
2018-09-12 13:53 ` [PATCH v2 06/11] arm: dts: hip04: " Suzuki K Poulose
2018-09-21 14:06 ` Wei Xu
2018-09-12 13:53 ` [PATCH v2 07/11] arm: dts: imx7: Update coresight binding " Suzuki K Poulose
2018-09-26 2:24 ` Shawn Guo
2018-09-12 13:53 ` [PATCH v2 08/11] arm: dts: omap: Update coresight bindings " Suzuki K Poulose
2018-09-20 22:01 ` Tony Lindgren
2018-09-12 13:53 ` [PATCH v2 09/11] arm: dts: qcom: " Suzuki K Poulose
2018-09-12 13:53 ` [PATCH v2 10/11] arm: dts: sama5d2: " Suzuki K Poulose
2018-09-19 17:12 ` Alexandre Belloni
2018-09-12 13:53 ` [PATCH v2 11/11] arm: dts: ste-dbx5x0: Update coresight bindings for hardware port Suzuki K Poulose
2018-09-14 8:43 ` Linus Walleij
2018-09-14 8:58 ` Suzuki K Poulose
2018-09-20 22:02 ` Linus Walleij
2018-09-21 9:24 ` Suzuki K Poulose
2018-09-19 23:29 ` [PATCH v2 00/11] dts: Update coresight device tree bindings Mathieu Poirier
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='CAK8P3a2WWFp5W5-7o-X3joOpSGgnK=s_ZyGev7gsVV0SjN0p0A@mail.gmail.com' \
--to=arnd@arndb.de \
--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).