All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Date: Fri, 16 Mar 2012 12:52:54 +0000	[thread overview]
Message-ID: <201203161252.54953.arnd@arndb.de> (raw)
In-Reply-To: <201203161333.22524.sr@denx.de>

On Friday 16 March 2012, Stefan Roese wrote:
> > I actually like to see the devices in there, and it already helped
> > figure out that there are two buses instead of just one. Maybe we
> > can agree on putting them in the file but commenting them out using
> > /* */ with an added notice that they will get enabled once we have
> > bindings?
> 
> It would be great to have a decision on this. I'm leaving for a short vacation 
> in a few hours and would like to have the new (hopefully final) patch out 
> before that.

It's not a show-stopper for me either way, your patches look great.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
Cc: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>,
	devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Date: Fri, 16 Mar 2012 12:52:54 +0000	[thread overview]
Message-ID: <201203161252.54953.arnd@arndb.de> (raw)
In-Reply-To: <201203161333.22524.sr-ynQEQJNshbs@public.gmane.org>

On Friday 16 March 2012, Stefan Roese wrote:
> > I actually like to see the devices in there, and it already helped
> > figure out that there are two buses instead of just one. Maybe we
> > can agree on putting them in the file but commenting them out using
> > /* */ with an added notice that they will get enabled once we have
> > bindings?
> 
> It would be great to have a decision on this. I'm leaving for a short vacation 
> in a few hours and would like to have the new (hopefully final) patch out 
> before that.

It's not a show-stopper for me either way, your patches look great.

	Arnd

  reply	other threads:[~2012-03-16 12:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  9:30 [PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards Stefan Roese
2012-03-16  9:30 ` Stefan Roese
2012-03-16  9:51 ` Viresh Kumar
2012-03-16  9:51   ` Viresh Kumar
2012-03-16 11:51   ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 11:51     ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 11:50 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 11:50   ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 12:09   ` Arnd Bergmann
2012-03-16 12:09     ` Arnd Bergmann
2012-03-16 12:33     ` Stefan Roese
2012-03-16 12:33       ` Stefan Roese
2012-03-16 12:52       ` Arnd Bergmann [this message]
2012-03-16 12:52         ` Arnd Bergmann
2012-03-16 12:57         ` Stefan Roese
2012-03-16 12:57           ` Stefan Roese
2012-03-16 12:20   ` Stefan Roese
2012-03-16 12:20     ` Stefan Roese
2012-03-16 12:14 ` Arnd Bergmann
2012-03-16 12:14   ` Arnd Bergmann
2012-03-16 12:34   ` Stefan Roese
2012-03-16 12:34     ` Stefan Roese

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=201203161252.54953.arnd@arndb.de \
    --to=arnd@arndb.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 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.