public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Fabien Parent <fparent@baylibre.com>,
	Nathan Chancellor <natechancellor@gmail.com>,
	arm-soc <arm@kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] soc: mediatek: soc driver updates for v5.2
Date: Mon, 29 Apr 2019 09:52:42 -0700	[thread overview]
Message-ID: <20190429165242.lzujqpkym4p43etl@localhost> (raw)
In-Reply-To: <269cf168-14c0-6a72-5078-0c8e307655eb@gmail.com>

On Tue, Apr 23, 2019 at 06:14:24PM +0200, Matthias Brugger wrote:
> Hi Olof and Arnd,
> 
> Below you can find the updates for soc drivers ready to be merged for v5.2.
> 
> Please take them into account.
> 
> Best regards,
> Matthias
> 
> ---
> 
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> 
>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
> tags/v5.1-next-soc
> 
> for you to fetch changes up to 89e28da82836530f1ac7a3a32fecc31f22d79b3e:
> 
>   soc: mediatek: pwrap: Zero initialize rdata in pwrap_init_cipher (2019-04-12
> 21:57:49 +0200)
> 
> ----------------------------------------------------------------
> pmic wrapper:
> - add mt8516 bindings
> - add mt8516 driver support
> - fix clang warning

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-29 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 16:14 [GIT PULL] soc: mediatek: soc driver updates for v5.2 Matthias Brugger
2019-04-29 16:52 ` 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=20190429165242.lzujqpkym4p43etl@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=fparent@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=natechancellor@gmail.com \
    /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