From: Paul Bolle <pebolle@tiscali.nl>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-hexagon@vger.kernel.org
Subject: Re: [PATCH v5 33/36] Hexagon: Add configuration and makefiles for the Hexagon architecture.
Date: Tue, 01 Nov 2011 19:59:52 +0100 [thread overview]
Message-ID: <1320173992.14409.193.camel@x61.thuisdomein> (raw)
In-Reply-To: <20111101172709.GA3035@codeaurora.org>
On Tue, 2011-11-01 at 12:27 -0500, Richard Kuo wrote:
> On Tue, Nov 01, 2011 at 10:30:46AM +0100, Paul Bolle wrote:
> > Is GENERIC_PENDING_IRQ also a pending project?
>
> Yes.
So, you'll move it up a line?
> > > +#config ZONE_DMA
> > > +# bool
> > > +# default y
> >
> > Why is this added commented out?
>
> We were using it before, but not anymore.
So, please drop it.
> > > +config STACKTRACE_SUPPORT
> > > + def_bool y
> > > + select STACKTRACE
> >
> > Some grepping suggests that the tracing infrastructure will "select
> > STACKTRACE" if the architecture sets STACKTRACE_SUPPORT (tile apparently
> > also gets this wrong). Have I grepped this correctly?
>
> Only if DEBUG_KMEMLEAK is selected apparently (?)
But "config TRACING" (in kernel/trace/Kconfig) also selects it if
STACKTRACE_SUPPORT is set. It seems GENERIC_TRACER is the hidden magic
here. GENERIC_TRACER is selected by the various tracer options - see
kernel/trace/Kconfig again, I'm unfamiliar with this stuff - and will
itself select TRACING. So if an arch has STACKTRACE_SUPPORT set it
doesn't have to select STACKTRACE itself. (Note that - except for tile -
no other arch selects STACKTRACE.)
But hopefully someone who doesn't have to grep the Kconfig files to
understand this, can tell us for sure.
> We felt it was better to remove the platform code for this submission
> as it was not exactly clean and did not use the devtree code. That's
> why it's commented out of the Makefiles.
If you really feel you need to add it, but commented out, perhaps a
comment can be added to keep people like me from submitting patches to
remove it.
Paul Bolle
next prev parent reply other threads:[~2011-11-01 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 23:55 Richard Kuo
2011-11-01 9:30 ` Paul Bolle
2011-11-01 17:27 ` Richard Kuo
2011-11-01 18:59 ` Paul Bolle [this message]
2011-11-01 21:17 ` Richard Kuo
-- strict thread matches above, loose matches on Subject: below --
2011-10-19 3:47 Richard Kuo
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=1320173992.14409.193.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuo@codeaurora.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®