From: Olof Johansson <olof@lixom.net>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: 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>,
Argus Lin <argus.lin@mediatek.com>
Subject: Re: [GIT PULL] ARM: mediatek: soc updates for v4.19
Date: Thu, 26 Jul 2018 22:08:32 +0200 [thread overview]
Message-ID: <CAOesGMiGQSTNBPuSuhhm1mT2eKxXNujRFk_KjtCOg_oTbOthsg@mail.gmail.com> (raw)
In-Reply-To: <97140b0d-ebc7-4fc2-e953-0709da22264b@gmail.com>
On Thu, Jul 26, 2018 at 10:20 AM, Matthias Brugger
<matthias.bgg@gmail.com> wrote:
> Hi Olof,
> Hi Arnd,
>
> This is the second attempt to send the pull request, as in the first one I sent
> the branch instead of the tag.
>
> Please have a look.
> Regards,
> Matthias
>
> ---
>
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
> tags/v4.18-next-soc
>
> for you to fetch changes up to 00673189b8b971c00417632ffe4c90ba9b4f2568:
>
> soc: mediatek: pwrap: add mt6351 driver for mt6797 SoCs (2018-07-16 15:50:17
> +0200)
>
> ----------------------------------------------------------------
> - add pmic wrapper support for mt6797
> - pmic wrapper fix chiper init
> - add support for pmic mt6351
Merged, thanks!
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mediatek: soc updates for v4.19
Date: Thu, 26 Jul 2018 22:08:32 +0200 [thread overview]
Message-ID: <CAOesGMiGQSTNBPuSuhhm1mT2eKxXNujRFk_KjtCOg_oTbOthsg@mail.gmail.com> (raw)
In-Reply-To: <97140b0d-ebc7-4fc2-e953-0709da22264b@gmail.com>
On Thu, Jul 26, 2018 at 10:20 AM, Matthias Brugger
<matthias.bgg@gmail.com> wrote:
> Hi Olof,
> Hi Arnd,
>
> This is the second attempt to send the pull request, as in the first one I sent
> the branch instead of the tag.
>
> Please have a look.
> Regards,
> Matthias
>
> ---
>
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
> tags/v4.18-next-soc
>
> for you to fetch changes up to 00673189b8b971c00417632ffe4c90ba9b4f2568:
>
> soc: mediatek: pwrap: add mt6351 driver for mt6797 SoCs (2018-07-16 15:50:17
> +0200)
>
> ----------------------------------------------------------------
> - add pmic wrapper support for mt6797
> - pmic wrapper fix chiper init
> - add support for pmic mt6351
Merged, thanks!
-Olof
next prev parent reply other threads:[~2018-07-26 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 20:51 [GIT PULL] ARM: mediatek: soc commits for v4.19 Matthias Brugger
2018-07-22 20:51 ` Matthias Brugger
2018-07-26 8:20 ` [GIT PULL] ARM: mediatek: soc updates " Matthias Brugger
2018-07-26 8:20 ` Matthias Brugger
2018-07-26 20:08 ` Olof Johansson [this message]
2018-07-26 20:08 ` 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=CAOesGMiGQSTNBPuSuhhm1mT2eKxXNujRFk_KjtCOg_oTbOthsg@mail.gmail.com \
--to=olof@lixom.net \
--cc=argus.lin@mediatek.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.