All of lore.kernel.org
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: move ARCH config definitions into mach dirs
Date: Fri, 31 Aug 2012 13:46:29 +0200	[thread overview]
Message-ID: <20120831114629.GB24490@glitch> (raw)
In-Reply-To: <20120831111138.GG18957@n2100.arm.linux.org.uk>

On Fri, Aug 31, 2012 at 12:11:38PM +0100, Russell King - ARM Linux wrote:
> On Fri, Aug 31, 2012 at 01:05:12PM +0200, Domenico Andreoli wrote:
> > On Thu, Aug 30, 2012 at 08:28:31PM +0100, Russell King - ARM Linux wrote:
> > > 
> > > I think what we need is arch/arm/include/debug, move the platform specific
> > > debug-macros headers into there, named using platform specific file names.
> > > Then we have the config system define a string-based config:
> > > 
> > > config DEBUG_LL_INCLUDE
> > > 	string
> > > 	default "<debug/icedcc.S>" if DEBUG_ICEDCC
> > > 	default "<debug/msm.S>" if DEBUG_MSM_UART1 || DEBUG_MSM_UART2 || DEBUG_MSM_UART3
> > > ... etc ...
> > > 	default "mach/debug-macros.S"
> > > 
> > > And then we can have the various assembly codes do:
> > > 
> > > #include CONFIG_DEBUG_LL_INCLUDE
> > > 
> > > Not only does this give a migration path, but it also gives folk a reason
> > > to move to the 'new way' if they want to be part of a multi-platform
> > > kernel - and it's a trivial thing to do.  Just move the include file,
> > > add an entry to the DEBUG_LL_INCLUDE entry and the "Kernel low-level
> > > debugging port" choice statement, and job done for both non-multi-platform
> > > and multi-platform kernels.
> > > 
> > > What's even nicer about this approach is it doesn't require everyone to
> > > change simultaneously - it can be done progressively as required.
> > 
> > This means that:
> 
> I'm not about to re-open the debate again.  Please go back and read the
> previous discussions during the last year about this where eventually
> agreement on this way forward was reached.  Thanks.

I don't want to reopen anything, it's only that I've clearly missed the
discussion (*) as also my patches in the area may show (**). So I really
wanted to understand if, for once, I've understood the thing correctly.

cheers,
Domenico

(*) I would have appreciated if you had pointed it to me in the only
comment you made on those patches but that's ok, it has been fun anyway

(**) http://lists.infradead.org/pipermail/linux-arm-kernel/2012-July/109457.html

  reply	other threads:[~2012-08-31 11:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 22:49 [PATCH 0/6] Initial multi-platform support Rob Herring
2012-08-29 22:49 ` [PATCH 1/6] ARM: move ARCH config definitions into mach dirs Rob Herring
2012-08-29 23:14   ` H Hartley Sweeten
2012-08-29 23:31   ` Russell King - ARM Linux
2012-08-30 15:18     ` Rob Herring
2012-08-30 16:45       ` Russell King - ARM Linux
2012-08-30 19:07         ` Rob Herring
2012-08-30 19:28           ` Russell King - ARM Linux
2012-08-31 11:05             ` Domenico Andreoli
2012-08-31 11:11               ` Russell King - ARM Linux
2012-08-31 11:46                 ` Domenico Andreoli [this message]
2012-09-01  0:48             ` Rob Herring
2012-09-02  8:49               ` Russell King - ARM Linux
2012-09-04 17:50                 ` Tony Lindgren
2012-08-29 22:49 ` [PATCH 2/6] ARM: introduce Kconfig.mach Rob Herring
2012-08-29 23:18   ` H Hartley Sweeten
2012-08-29 22:49 ` [PATCH 3/6] ARM: picoxcell: header fixes for multi-platform Rob Herring
2012-08-29 22:49 ` [PATCH 4/6] ARM: vexpress: remove dependency on mach/* headers Rob Herring
2012-08-29 22:49 ` [PATCH 5/6] ARM: initial multiplatform support Rob Herring
2012-08-29 22:50 ` [PATCH 6/6] ARM: update defconfigs Rob Herring
2012-08-31 18:12 ` [PATCH v2] ARM: initial multiplatform support Rob Herring
2012-09-03 16:34   ` Arnd Bergmann
2012-09-03 21:58     ` Rob Herring
2012-09-04  6:56       ` Arnd Bergmann
2012-09-04 22:40         ` Rob Herring
2012-09-05 10:36           ` Arnd Bergmann
2012-09-05 13:25             ` Rob Herring
2012-09-05 13:33               ` Arnd Bergmann

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=20120831114629.GB24490@glitch \
    --to=cavokz@gmail.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.