All of lore.kernel.org
 help / color / mirror / Atom feed
From: srinivas.kandagatla@st.com (Srinivas KANDAGATLA)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: STi: remove unused Kconfig parameters
Date: Wed, 18 Sep 2013 07:35:13 +0100	[thread overview]
Message-ID: <523949A1.7080600@st.com> (raw)
In-Reply-To: <1379474622-4715-1-git-send-email-michael.opdenacker@free-electrons.com>

Hi Michael.
On 18/09/13 04:23, Michael Opdenacker wrote:
> This patch proposes to remove the 'SOC_STIH415' and 'SOC_STIH416'
> parameters, which are used nowhere else in the source code
> and Makefiles.
> 
> Will they be needed in code that hasn't been submitted yet?
Yes, we will be using it in future patches, for something like reset
controller.
Also I am planning to use in dts/Makefiles so that we can build dtbs for
only selected SOC.

Thanks,
srini

WARNING: multiple messages have this Message-ID (diff)
From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: stuart.menefy@st.com, linux-arm-kernel@lists.infradead.org,
	kernel@stlinux.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: STi: remove unused Kconfig parameters
Date: Wed, 18 Sep 2013 07:35:13 +0100	[thread overview]
Message-ID: <523949A1.7080600@st.com> (raw)
In-Reply-To: <1379474622-4715-1-git-send-email-michael.opdenacker@free-electrons.com>

Hi Michael.
On 18/09/13 04:23, Michael Opdenacker wrote:
> This patch proposes to remove the 'SOC_STIH415' and 'SOC_STIH416'
> parameters, which are used nowhere else in the source code
> and Makefiles.
> 
> Will they be needed in code that hasn't been submitted yet?
Yes, we will be using it in future patches, for something like reset
controller.
Also I am planning to use in dts/Makefiles so that we can build dtbs for
only selected SOC.

Thanks,
srini



  reply	other threads:[~2013-09-18  6:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  3:23 [PATCH] ARM: STi: remove unused Kconfig parameters Michael Opdenacker
2013-09-18  3:23 ` Michael Opdenacker
2013-09-18  6:35 ` Srinivas KANDAGATLA [this message]
2013-09-18  6:35   ` Srinivas KANDAGATLA
2013-09-18 11:52   ` Michael Opdenacker
2013-09-18 11:52     ` Michael Opdenacker

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=523949A1.7080600@st.com \
    --to=srinivas.kandagatla@st.com \
    --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.