linux-samsung-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
	vireshk@kernel.org, linux-pm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, b.zolnierkie@samsung.com,
	m.szyprowski@samsung.com
Subject: Re: [PATCH 1/3] soc: samsung: Drop "syscon" compatible requirement from the chipid driver
Date: Mon, 28 Oct 2019 18:35:38 +0100	[thread overview]
Message-ID: <20191028173538.GA14395@kozik-lap> (raw)
In-Reply-To: <20191028152050.10220-1-s.nawrocki@samsung.com>

On Mon, Oct 28, 2019 at 04:20:48PM +0100, Sylwester Nawrocki wrote:
> As we dropped the requirement of "syscon" compatible in the chipid
> nodes rework code acquiring the regmap to use device_node_to_regmap()
> rather than syscon_node_to_regmap().
> 
> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
> ---
>  drivers/soc/samsung/exynos-chipid.c | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)

Thanks, applied.

Best regards,
Krzysztof


      parent reply	other threads:[~2019-10-28 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191028152057eucas1p1d6b4252e9ce3f15c0d81e6941a62d2be@eucas1p1.samsung.com>
2019-10-28 15:20 ` [PATCH 1/3] soc: samsung: Drop "syscon" compatible requirement from the chipid driver Sylwester Nawrocki
     [not found]   ` <CGME20191028152059eucas1p2b48166c35f61dfc8edfa99f54434e8ee@eucas1p2.samsung.com>
2019-10-28 15:20     ` [PATCH 2/3] ARM: dts: exynos: Remove syscon compatible from chipid node on Exynos5 Sylwester Nawrocki
2019-12-11 18:20       ` Krzysztof Kozlowski
     [not found]   ` <CGME20191028152100eucas1p2ed6bd2d53670c85f6bf550af0631a55a@eucas1p2.samsung.com>
2019-10-28 15:20     ` [PATCH 3/3] dt-bindings: arm: samsung: Drop syscon compatible from CHIPID binding Sylwester Nawrocki
2019-10-28 15:47       ` Krzysztof Kozlowski
2019-11-06  3:28       ` Rob Herring
2019-10-28 17:35   ` Krzysztof Kozlowski [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=20191028173538.GA14395@kozik-lap \
    --to=krzk@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robh+dt@kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=vireshk@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).