From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] ARM: Add a generic macro for declaring proc_info structs
Date: Mon, 13 Jun 2011 14:48:06 +0100 [thread overview]
Message-ID: <20110613134806.GA8498@arm.com> (raw)
In-Reply-To: <20110613131257.GA13643@n2100.arm.linux.org.uk>
On Mon, Jun 13, 2011 at 02:12:57PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jun 13, 2011 at 02:10:08PM +0100, Dave Martin wrote:
> > Using macros such as you suggest would force a consistent naming on
> > different CPUs' helper functions, which actually seems rather a good thing.
> > A possible downside is that the relationship between those functions
> > and the macro becomes invisible in proc-*.S (though a very brief comment
> > or two could easibly address that).
>
> The consistent naming is already required for the !MULTI_CPU, etc.
> Same for the cache and tlb structs.
>
> The processor structure has less strict requirements though.
OK, well I might have a go at this for the CPU func structs at some point,
and see how it turns out.
Cheers
---Dave
prev parent reply other threads:[~2011-06-13 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 17:21 [RFC PATCH 0/2] ARM: Add a generic macro for declaring proc_info structs Dave Martin
2011-06-09 17:21 ` [RFC PATCH 1/2] " Dave Martin
2011-06-09 17:21 ` [RFC PATCH 2/2] ARM: proc-v7: Use the new proc_info declaration macro Dave Martin
2011-06-09 17:38 ` [RFC PATCH 0/2] ARM: Add a generic macro for declaring proc_info structs Russell King - ARM Linux
2011-06-10 8:57 ` Dave Martin
2011-06-12 8:22 ` Russell King - ARM Linux
2011-06-12 15:14 ` Russell King - ARM Linux
2011-06-13 13:10 ` Dave Martin
2011-06-13 13:12 ` Russell King - ARM Linux
2011-06-13 13:48 ` Dave Martin [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=20110613134806.GA8498@arm.com \
--to=dave.martin@linaro.org \
--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.