From: Richard Kuo <rkuo@codeaurora.org>
To: Paul Bolle <pebolle@tiscali.nl>
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, 1 Nov 2011 16:17:59 -0500 [thread overview]
Message-ID: <20111101211759.GB3035@codeaurora.org> (raw)
In-Reply-To: <1320173992.14409.193.camel@x61.thuisdomein>
On Tue, Nov 01, 2011 at 07:59:52PM +0100, Paul Bolle wrote:
> 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.
Yes to both of these.
> 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.
Ah... Well, if nothing else, I'll just try not setting it and see if it
works as it seems to be intended.
> 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.
Sounds reasonable. I'll either add a comment or just remove it
altogether (which is the long term goal).
Not that I mind getting patches, of course.
I'll have all these fixed in my tree and push them out when I can.
Thanks,
Richard Kuo
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-11-01 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 23:55 [PATCH v5 33/36] Hexagon: Add configuration and makefiles for the Hexagon architecture Richard Kuo
2011-11-01 9:30 ` Paul Bolle
2011-11-01 17:27 ` Richard Kuo
2011-11-01 18:59 ` Paul Bolle
2011-11-01 21:17 ` Richard Kuo [this message]
-- 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=20111101211759.GB3035@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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 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.