From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Adrian Bunk <bunk@kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: [2.6 patch] kconfig-language.txt: remove bogus hint
Date: Sun, 4 May 2008 21:08:35 +0200 [thread overview]
Message-ID: <20080504190835.GB23619@uranus.ravnborg.org> (raw)
In-Reply-To: <481DF887.5030101@oracle.com>
On Sun, May 04, 2008 at 10:55:19AM -0700, Randy Dunlap wrote:
> >
> >The idiom has use cases, but you need the following prerequisites:
> >- A and B are tristates
> >- B does not depend on A
> >- C is a bool with the semantics "enable feature C in B"
> >
> >And I doubt you can put that into a useful hint.
>
> OK, sounds like the patch is good then.
Thanks for the explanations.
Patch applied.
Sam
prev parent reply other threads:[~2008-05-04 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 23:15 [2.6 patch] kconfig-language.txt: remove bogus hint Adrian Bunk
2008-05-04 6:17 ` Sam Ravnborg
2008-05-04 8:01 ` Adrian Bunk
2008-05-04 11:27 ` Sam Ravnborg
2008-05-04 12:10 ` Adrian Bunk
2008-05-04 12:26 ` Sam Ravnborg
2008-05-04 17:25 ` Randy Dunlap
2008-05-04 17:51 ` Adrian Bunk
2008-05-04 17:55 ` Randy Dunlap
2008-05-04 19:08 ` Sam Ravnborg [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=20080504190835.GB23619@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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