From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Date: Thu, 15 Mar 2012 14:12:46 +0530 [thread overview]
Message-ID: <4F61AB86.5010204@st.com> (raw)
In-Reply-To: <201203150941.02822.sr@denx.de>
On 3/15/2012 2:11 PM, Stefan Roese wrote:
> So why don't we make an even bigger "cut", and remove the non-DT SPEAr600
> files/data completely now? If you give me your ACK on this, I'll squash this
> into my patch as well, resulting in a nice diffstat.
My ack is already with you :)
Just go ahead, float the new version and i will ack it.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
To: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
Cc: "devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org"
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
spear-devel <spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Date: Thu, 15 Mar 2012 14:12:46 +0530 [thread overview]
Message-ID: <4F61AB86.5010204@st.com> (raw)
In-Reply-To: <201203150941.02822.sr-ynQEQJNshbs@public.gmane.org>
On 3/15/2012 2:11 PM, Stefan Roese wrote:
> So why don't we make an even bigger "cut", and remove the non-DT SPEAr600
> files/data completely now? If you give me your ACK on this, I'll squash this
> into my patch as well, resulting in a nice diffstat.
My ack is already with you :)
Just go ahead, float the new version and i will ack it.
--
viresh
next prev parent reply other threads:[~2012-03-15 8:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 15:00 [PATCH v2] ARM: SPEAr600: Add device-tree support to SPEAr600 boards Stefan Roese
2012-03-14 15:00 ` Stefan Roese
2012-03-14 15:54 ` Arnd Bergmann
2012-03-14 15:54 ` Arnd Bergmann
2012-03-14 16:21 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-14 16:21 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-14 16:49 ` Stefan Roese
2012-03-14 16:49 ` Stefan Roese
2012-03-14 17:24 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-14 17:24 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-14 19:01 ` Stefan Roese
2012-03-14 19:01 ` Stefan Roese
2012-03-15 15:32 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-15 15:32 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-15 8:19 ` Viresh Kumar
2012-03-15 8:19 ` Viresh Kumar
2012-03-15 8:41 ` Stefan Roese
2012-03-15 8:41 ` Stefan Roese
2012-03-15 8:42 ` Viresh Kumar [this message]
2012-03-15 8:42 ` Viresh Kumar
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=4F61AB86.5010204@st.com \
--to=viresh.kumar@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.