All of lore.kernel.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: sti: SOC_STIH407 and STIH407_RESET?
Date: Mon, 10 Nov 2014 10:56:49 +0000	[thread overview]
Message-ID: <20141110105649.GW21424@x1> (raw)
In-Reply-To: <1415614934.4862.22.camel@x220>

On Mon, 10 Nov 2014, Paul Bolle wrote:
> Your commit c27321141915 ("ARM: sti: Add STiH407 Kconfig entry to select
> STIH407_RESET") was included in today's linux-next (ie, next-20141110).
> It adds a Kconfig entry for SOC_STIH407. That entry selects
> STIH407_RESET.
> 
> There's no Kconfig symbol STIH407_RESET. And there's nothing in
> next-20141110 that cares about SOC_STIH407. So this entry is currently a
> nop.

You're right, thanks for your diligence.

> I assume that there are one or more patches queued that make this entry
> do something. Is that correct?

That is also true.  Patch is en route.

It should be coming through the reset tree and arm-soc.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Peter Griffin <peter.griffin@linaro.org>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
	Maxime Coquelin <maxime.coquelin@st.com>,
	Patrice Chotard <patrice.chotard@st.com>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org, kernel@stlinux.com,
	linux-kernel@vger.kernel.org
Subject: Re: ARM: sti: SOC_STIH407 and STIH407_RESET?
Date: Mon, 10 Nov 2014 10:56:49 +0000	[thread overview]
Message-ID: <20141110105649.GW21424@x1> (raw)
In-Reply-To: <1415614934.4862.22.camel@x220>

On Mon, 10 Nov 2014, Paul Bolle wrote:
> Your commit c27321141915 ("ARM: sti: Add STiH407 Kconfig entry to select
> STIH407_RESET") was included in today's linux-next (ie, next-20141110).
> It adds a Kconfig entry for SOC_STIH407. That entry selects
> STIH407_RESET.
> 
> There's no Kconfig symbol STIH407_RESET. And there's nothing in
> next-20141110 that cares about SOC_STIH407. So this entry is currently a
> nop.

You're right, thanks for your diligence.

> I assume that there are one or more patches queued that make this entry
> do something. Is that correct?

That is also true.  Patch is en route.

It should be coming through the reset tree and arm-soc.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2014-11-10 10:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 10:22 ARM: sti: SOC_STIH407 and STIH407_RESET? Paul Bolle
2014-11-10 10:22 ` Paul Bolle
2014-11-10 10:27 ` Maxime Coquelin
2014-11-10 10:27   ` Maxime Coquelin
2014-11-10 10:49   ` Paul Bolle
2014-11-10 10:49     ` Paul Bolle
2014-11-10 11:10     ` Maxime Coquelin
2014-11-10 11:10       ` Maxime Coquelin
2014-11-10 10:56 ` Lee Jones [this message]
2014-11-10 10:56   ` Lee Jones

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=20141110105649.GW21424@x1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.