From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] sprd dts for kernel v4.20-rc1
Date: Fri, 2 Nov 2018 11:32:46 -0700 [thread overview]
Message-ID: <20181102183246.r5xxwsic2mxwihsi@localhost> (raw)
In-Reply-To: <1539854253-4784-1-git-send-email-chunyan.zhang@unisoc.com>
On Thu, Oct 18, 2018 at 05:17:33PM +0800, Chunyan Zhang wrote:
> Hi Arnd,
>
> For 4.20-rc1 there's one patch only for sprd devicetree, please pull from my git tree:
>
> https://github.com/lyrazhang/linux.git m-v4.19-rc1
>
> Please let me know if there's some problem.
>
> Thanks,
> Chunyan
>
> ----------------------------------------------------------------
>
> Suzuki K Poulose (1):
> arm64: dts: sc9836/sc9860: Update coresight bindings for hardware
> ports
>
> arch/arm64/boot/dts/sprd/sc9836.dtsi | 78 +++++++------
> arch/arm64/boot/dts/sprd/sc9860.dtsi | 215 ++++++++++++++++++-----------------
> 2 files changed, 151 insertions(+), 142 deletions(-)
Hi,
This came in right before the merge window so it wasn't included since
it's more of a cleanup. Please resend it after -rc1 is out and we'll be
happy to queue it up for 4.21.
Also, when you do, please use "git request-pull" to generate your pull request.
That contains more information about the base, etc, and is generally how we
prefer to get pull requests. When you do, also use a signed tag instead of just
a branch head for the pull request. Let us know if you need help on usage of
that.
Thanks!
-Olof
next prev parent reply other threads:[~2018-11-02 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 9:17 [GIT PULL] sprd dts for kernel v4.20-rc1 Chunyan Zhang
2018-11-01 6:36 ` Chunyan Zhang
2018-11-01 8:35 ` Chunyan Zhang
2018-11-02 18:32 ` Olof Johansson [this message]
2018-11-05 9:54 ` Suzuki K Poulose
2018-11-30 15:18 ` Rob Herring
2018-11-30 19:48 ` Olof Johansson
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=20181102183246.r5xxwsic2mxwihsi@localhost \
--to=olof@lixom.net \
--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).