From: Olof Johansson <olof@lixom.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
ARM-SoC Maintainers <arm@kernel.org>,
Kukjin Kim <kgene@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
linux-samsung-soc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL 3/4] ARM: exynos: soc/mach for v4.20, second round
Date: Fri, 12 Oct 2018 11:12:34 -0700 [thread overview]
Message-ID: <CAOesGMj2m9pOsDhY92Q-ycbCQXViHatrk-SvqO+TqdzDw7DJZA@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a2+wyge4=eCxJps0Ar3bYFrqjvdMakiYHBPmn3p63+GDg@mail.gmail.com>
On Thu, Oct 11, 2018 at 7:02 AM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On 10/10/18, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > Hi,
> >
> > On top of previous pull request.
> >
> > ----------------------------------------------------------------
> > Samsung mach/soc changes for v4.20, second round
> >
> > 1. Disable SAMSUNG_PM_CHECK Kconfig feature incompatible with Exynos.
> >
>
> I suspect Olof made a small mistake when he pulled the previous branch
> into next/dt instead of next/soc, so I ended up pulling the new branch
> with all commits into next/soc again.
>
> Nothing harmful happened and you did everything right, I was just
> a bit confused by this.
Indeed, thanks for catching that.
-Olof
next prev parent reply other threads:[~2018-10-12 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 18:25 [GIT PULL 0/4] arm: exynos: Last round for v4.20 Krzysztof Kozlowski
2018-10-10 18:25 ` [GIT PULL 1/4] ARM: dts: exynos: Second " Krzysztof Kozlowski
2018-10-11 14:04 ` Arnd Bergmann
2018-10-10 18:25 ` [GIT PULL 2/4] arm64: dts: exynos: Stuff " Krzysztof Kozlowski
2018-10-11 14:06 ` Arnd Bergmann
2018-10-10 18:25 ` [GIT PULL 3/4] ARM: exynos: soc/mach for v4.20, second round Krzysztof Kozlowski
2018-10-11 14:02 ` Arnd Bergmann
2018-10-12 18:12 ` Olof Johansson [this message]
2018-10-10 18:25 ` [PATCH / PULL 4/4] arm64: exynos: Enable generic power domain support Krzysztof Kozlowski
2018-10-11 13:27 ` Arnd Bergmann
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=CAOesGMj2m9pOsDhY92Q-ycbCQXViHatrk-SvqO+TqdzDw7DJZA@mail.gmail.com \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.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).