linux-samsung-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Olof Johansson <olof@lixom.net>,
	Kevin Hilman <khilman@kernel.org>,
	arm@kernel.org, Kukjin Kim <kgene@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [GIT PULL] ARM: exynos: Late mach/soc for v4.10
Date: Wed, 04 Jan 2017 16:14:00 +0100	[thread overview]
Message-ID: <2234017.fClA8kpiX3@wuerfel> (raw)
In-Reply-To: <1482003132-8844-1-git-send-email-krzk@kernel.org>

On Saturday, December 17, 2016 9:32:12 PM CET Krzysztof Kozlowski wrote:
> After our discussions about not-breaking out-of-tree DTB with SCU
> change in DeviceTree, I prepared an updated pull request without
> the questioned changes.
> 
> Ten days ago I prepared a tag, pushed it... and apparently forgot to send pull
> request. At least, I don't have such email in my outbox. Dunno.
> 
> So let's send it now, better late then never. With just few commits (without
> the DT SCU changes). These were sitting in the next for very long.

Sorry for the delay. The patches in here are all straightforward, so
I'm applying them for fixes now.

	Arnd

      parent reply	other threads:[~2017-01-04 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-17 19:32 [GIT PULL] ARM: exynos: Late mach/soc for v4.10 Krzysztof Kozlowski
2016-12-30 15:53 ` Krzysztof Kozlowski
     [not found]   ` <CGME20170102092044epcas1p3cbe831b7b6528f818b034d73c85dbe7d@epcas1p3.samsung.com>
2017-01-02  9:20     ` Sylwester Nawrocki
2017-01-02 15:56       ` Krzysztof Kozlowski
2017-01-02 17:25         ` Sylwester Nawrocki
2017-01-02 17:35           ` Krzysztof Kozlowski
2017-01-04 15:14 ` Arnd Bergmann [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=2234017.fClA8kpiX3@wuerfel \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=javier@osg.samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@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 \
    --cc=olof@lixom.net \
    /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).