public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Pawel Moll <mail@pawelmoll.com>
Cc: Simon Horman <horms@verge.net.au>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
	linux-mmc@vger.kernel.org,
	Yusuke Goda <yusuke.goda.sx@renesas.com>,
	Chris Ball <cjb@laptop.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mmc, ARM: Add zboot from MMC support for SuperH Mobile ARM
Date: Tue, 11 Jan 2011 00:45:14 +0900	[thread overview]
Message-ID: <20110110154514.GC3760@linux-sh.org> (raw)
In-Reply-To: <c1e9db480d82d1804930ddcc7bb0db02@rootnode.net>

On Mon, Jan 10, 2011 at 10:10:19AM +0000, Pawel Moll wrote:
> On Mon, 10 Jan 2011 07:50:42 +0900, Simon Horman <horms@verge.net.au> 
> wrote:
> >>>  Documentation/arm/SH-Mobile/Makefile              |    8 +
> >>>  Documentation/arm/SH-Mobile/vrl4.c                |  169 
> >>+++++++++++++++++++++
> >>How about putting those two into "tools" (in particular "tools/arm")
> >>instead of "Documentation"?
> >>Just a thought... ;-)
> >
> >Thats fine by me except that tools/arm doesn't exist yet.
> >It would be good to get some consensus before creating it.
> 
> I think there is consensus regarding "tools" as a place for user-space 
> tools - eg. perf tools used to live in "Documentation/..." and then were 
> moved to "tools/perf".
> 
> Now, whether your stuff should be in "tools/SH-Mobile" or 
> "tools/arm/SH-Mobile", I have no opinion ;-)
> 
I agree that this is a worthwhile direction to move to, but we're a long
way from a consensus. x86 has traditionally littered scripts/ and others
have sunk to arch/<foo>/tools hostprogs abuse and so forth. perf is a bit
of a special case in that it's fairly architecture agnostic. 

  reply	other threads:[~2011-01-10 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 12:49 [PATCH] mmc, ARM: Add zboot from MMC support for SuperH Mobile ARM Simon Horman
2011-01-09 16:12 ` Paweł Moll
2011-01-09 22:50   ` Simon Horman
2011-01-10 10:10     ` Pawel Moll
2011-01-10 15:45       ` Paul Mundt [this message]
2011-01-10 22:41         ` Simon Horman
2011-01-09 23:12 ` Russell King - ARM Linux
2011-01-09 23:52   ` Simon Horman
  -- strict thread matches above, loose matches on Subject: below --
2011-01-09 12:39 Simon Horman

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=20110110154514.GC3760@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=cjb@laptop.org \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mail@pawelmoll.com \
    --cc=yusuke.goda.sx@renesas.com \
    /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