public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@aj.id.au>, arm <arm@kernel.org>,
	linux-aspeed@lists.ozlabs.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: aspeed: dts changes for 5.2
Date: Sun, 28 Apr 2019 12:17:21 -0700	[thread overview]
Message-ID: <20190428191721.v76bkirt4tiufnfd@localhost> (raw)
In-Reply-To: <CACPK8XdevZ9LHtVVu=fHbTxSKfDugym3jT0ueKEpa9qhLYbFnw@mail.gmail.com>

On Fri, Apr 05, 2019 at 03:47:38AM +0000, Joel Stanley wrote:
> Hello ARM Maintainers,
> 
> Here's the first ASPEED device tree pull request for 5.2. There might be a
> second one later as I pushed out a pair of patches for review today.
> 
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> 
>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git \
>     tags/aspeed-5.2-devicetree

Thanks for easing copy-paste!

> 
> for you to fetch changes up to 6d00c6f8d2e781e3c821fc9c614f404cc981804d:
> 
>   ARM: dts: aspeed: Add RTC node (2019-04-05 14:08:20 +1030)
> 
> ----------------------------------------------------------------
> ASPEED device tree updates for 5.2
> 
>  - RTC and GFX DRM driver went upstream this cycle
> 
>  - Miscellaneous board updates for Facebook and IBM BMCs

Merged, thanks!


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-04-28 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05  3:47 [GIT PULL] ARM: aspeed: dts changes for 5.2 Joel Stanley
2019-04-28 19:17 ` 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=20190428191721.v76bkirt4tiufnfd@localhost \
    --to=olof@lixom.net \
    --cc=andrew@aj.id.au \
    --cc=arm@kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.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