linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] berlin dt64 changes for v4.18
Date: Fri, 25 May 2018 14:55:58 -0700	[thread overview]
Message-ID: <20180525215558.yc5anyapi2xcq4ir@localhost> (raw)
In-Reply-To: <20180524160420.35da91b5@xhacker.debian>

On Thu, May 24, 2018 at 04:04:20PM +0800, Jisheng Zhang wrote:
> Hi,
> 
> Here is the pull request for berlin dt64 changes for v4.18.
> 
> Thanks,
> Jisheng
> 
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
> 
>   Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jszhang/linux-berlin.git tags/berlin64-dt-for-v4.18
> 
> for you to fetch changes up to 031106ce95a201f6dd4c5ebf35abb900cf34e2ba:
> 
>   arm64: dts: move berlin SoC files from marvell dir to synaptics dir (2018-05-24 13:25:45 +0800)
> 
> ----------------------------------------------------------------
> Berlin64 DT changes for v4.18
> 
>  - use SPDX-License-Identifier for dts(i) files
>  - move berlin SoC dts(i) files from marvell dir to synaptics dir

Usually we don't do renames, but this is a pure file move so it's not causing
significant disturbance, and there seems to be quite little overlap between
this and other marvell platforms on includes, etc, so it seems ok.


Merged, thanks!


-Olof

      reply	other threads:[~2018-05-25 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  8:04 [GIT PULL] berlin dt64 changes for v4.18 Jisheng Zhang
2018-05-25 21:55 ` Olof Johansson [this message]

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=20180525215558.yc5anyapi2xcq4ir@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).