From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, domen.puncer@telargo.com
Subject: Re: [PATCH v2 2/7] rheap: Changes config mechanism
Date: Mon, 15 Oct 2007 08:06:10 -0600 [thread overview]
Message-ID: <fa686aa40710150706v1175b23bg83d8ee12e939cc8d@mail.gmail.com> (raw)
In-Reply-To: <5D5FEAFA-AFB9-4F8D-941E-11686E8992F4@kernel.crashing.org>
On 10/15/07, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Oct 15, 2007, at 8:55 AM, Grant Likely wrote:
>
> > On 10/15/07, Kumar Gala <galak@kernel.crashing.org> wrote:
> >>
> >> On Oct 13, 2007, at 11:41 PM, Grant Likely wrote:
> >>
> >>> From: Sylvain Munaut <tnt@246tNt.com>
> >>>
> >>> Instead of having in the makefile all the option that
> >>> requires rheap, we define a configuration symbol
> >>> and when needed we make sure it's selected.
> >>>
> >>> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
> >>> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> >>> ---
> >>>
> >>> +
> >>> +config PPC_LIB_RHEAP
> >>
> >> we should really have help for this option.
> >
> > This is a non-user-selectable option; none of the other
> > non-user-selectable options have help text.
>
> I don't see why we can't let users select it (saying that
> differently, we should let users have this ability)
Sure; but not in this patch. This patch just changes from one fixed
method for selecting rheap to another.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-15 14:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 4:41 [PATCH v2 0/7] 2nd respin of bestcomm patches Grant Likely
2007-10-14 4:41 ` [PATCH v2 1/7] exports rheap symbol to modules Grant Likely
2007-10-14 4:41 ` [PATCH v2 2/7] rheap: Changes config mechanism Grant Likely
2007-10-15 13:43 ` Kumar Gala
2007-10-15 13:55 ` Grant Likely
2007-10-15 14:03 ` Kumar Gala
2007-10-15 14:06 ` Grant Likely [this message]
2007-10-15 14:53 ` Timur Tabi
2007-10-15 14:54 ` Kumar Gala
2007-10-15 14:54 ` Timur Tabi
2007-10-15 15:09 ` Grant Likely
2007-10-14 4:42 ` [PATCH v2 3/7] mpc52xx: Update mpc52xx_psc structure with B revision changes Grant Likely
2007-10-14 4:42 ` [PATCH v2 4/7] bestcomm: core bestcomm support for Freescale MPC5200 Grant Likely
2007-10-14 11:33 ` Sven Luther
2007-10-14 20:22 ` Grant Likely
2007-10-14 20:25 ` Sven Luther
2007-10-14 21:23 ` Grant Likely
2007-10-15 6:12 ` Sven Luther
2007-10-15 11:55 ` Matt Sealey
2007-10-15 14:04 ` Grant Likely
2007-10-15 20:53 ` Matt Sealey
2007-10-15 20:55 ` Matt Sealey
2007-10-15 21:06 ` Grant Likely
2007-10-16 13:21 ` tnt
2007-10-15 14:06 ` Kumar Gala
2007-10-15 14:20 ` Grant Likely
2007-10-15 14:39 ` Matt Sealey
2007-10-14 4:42 ` [PATCH v2 5/7] bestcomm: ATA task support Grant Likely
2007-10-14 4:42 ` [PATCH v2 6/7] bestcomm: FEC " Grant Likely
2007-10-14 4:42 ` [PATCH v2 7/7] bestcomm: GenBD " Grant Likely
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=fa686aa40710150706v1175b23bg83d8ee12e939cc8d@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=domen.puncer@telargo.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).