linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] ARM: STi reset controller support
Date: Tue, 25 Feb 2014 12:15:54 +0100	[thread overview]
Message-ID: <1393326954.4156.3.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <530C76F0.8000909@st.com>

Hi Srinivas,

Am Dienstag, den 25.02.2014, 10:56 +0000 schrieb srinivas kandagatla:
> Thankyou Philipp,
> On 25/02/14 09:47, Philipp Zabel wrote:
> >> No, the context is lost, the IP needs re-initialization.
> > alright then, I'll add them to the queue.
> Thats Great..
> Can I ask your Ack on these patches so that I can request Arnd/Olof to
> take these patches via arm-soc tree.
> 
> Hi Arnd/Olof,
> 
> I have few more DT patches which depend on the reset controller header
> file. Is is possible to take the reset controller patches with Philipp's
> Acks via arm-soc tree?

That's fine with me, too. Shall I back the patches out of the reset
queue, then?

Acked-by: Philipp Zabel <p.zabel@pengutronix.de>

regards
Philipp

      reply	other threads:[~2014-02-25 11:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 10:50 [PATCH v1 0/6] STi reset controller suppport Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 1/6] drivers: reset: STi SoC system configuration reset controller support Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 2/6] drivers: reset: Reset controller driver for STiH415 Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 3/6] drivers: reset: Reset controller driver for STiH416 Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 4/6] drivers: reset: stih415: add softreset controller Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 5/6] drivers: reset: stih416: " Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 6/6] ARM: STi: Add reset controller support to mach-sti Kconfig Srinivas Kandagatla
2014-02-03 14:27 ` [PATCH v2 0/6] ARM: STi reset controller support srinivas.kandagatla at st.com
2014-02-03 14:28   ` [PATCH v2 1/6] drivers: reset: STi SoC system configuration " srinivas.kandagatla at st.com
2014-02-03 14:28   ` [PATCH v2 2/6] drivers: reset: Reset controller driver for STiH415 srinivas.kandagatla at st.com
2014-02-03 14:28   ` [PATCH v2 3/6] drivers: reset: Reset controller driver for STiH416 srinivas.kandagatla at st.com
2014-02-03 14:28   ` [PATCH v2 4/6] drivers: reset: stih415: add softreset controller srinivas.kandagatla at st.com
2014-02-03 14:28   ` [PATCH v2 5/6] drivers: reset: stih416: " srinivas.kandagatla at st.com
2014-02-03 14:29   ` [PATCH v2 6/6] ARM: STi: Add reset controller support to mach-sti Kconfig srinivas.kandagatla at st.com
2014-02-05  9:28   ` [PATCH v2 0/6] ARM: STi reset controller support Philipp Zabel
2014-02-07 12:54     ` srinivas kandagatla
2014-02-19 13:57       ` Maxime Coquelin
2014-02-24 10:33         ` Philipp Zabel
2014-02-24 14:03           ` srinivas kandagatla
2014-02-24 15:16             ` Philipp Zabel
2014-02-25  9:08               ` srinivas kandagatla
2014-02-25  9:47                 ` Philipp Zabel
2014-02-25 10:56                   ` srinivas kandagatla
2014-02-25 11:15                     ` Philipp Zabel [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=1393326954.4156.3.camel@pizza.hi.pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --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 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).