From: Russell King <rmk@arm.linux.org.uk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Where's the documentation for Kconfig?
Date: Fri, 1 Nov 2002 20:35:46 +0000 [thread overview]
Message-ID: <20021101203546.C26989@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20021101203033.GA5773@opus.bloom.county>; from trini@kernel.crashing.org on Fri, Nov 01, 2002 at 01:30:33PM -0700
On Fri, Nov 01, 2002 at 01:30:33PM -0700, Tom Rini wrote:
> On a related question, can we now have 'UL', etc in a hex statement /
> question?
No thanks - that'll stop it being used in linker scripts.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-11-01 20:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 13:43 Where's the documentation for Kconfig? Matthew Wilcox
2002-10-31 14:43 ` Roman Zippel
2002-10-31 15:27 ` Christoph Hellwig
2002-10-31 16:03 ` Roman Zippel
2002-11-01 8:23 ` Rusty Russell
2002-11-01 12:52 ` Russell King
2002-11-01 13:50 ` Roman Zippel
2002-11-01 19:31 ` Russell King
2002-11-01 20:30 ` Tom Rini
2002-11-01 20:35 ` Russell King [this message]
2002-11-01 20:42 ` Tom Rini
2002-11-01 20:46 ` Russell King
2002-11-01 23:32 ` Tom Rini
2002-11-01 23:52 ` Roman Zippel
2002-11-02 0:07 ` Tom Rini
2002-11-02 0:46 ` Roman Zippel
2002-11-01 20:35 ` Roman Zippel
[not found] ` <20020625221306.GA439@free.fr>
[not found] ` <Pine.LNX.4.44.0211021254420.6949-100000@serv>
2002-11-02 13:20 ` Kconfig (qt) -> Gconfig (gtk+) Romain Lievin
2002-11-02 14:45 ` Roman Zippel
2002-11-02 18:56 ` qconf buglet James H. Cloos Jr.
2002-11-02 19:48 ` Roman Zippel
2002-11-02 23:40 ` James H. Cloos Jr.
2002-11-02 13:51 ` Where's the documentation for Kconfig? Erik Andersen
2002-11-02 19:26 ` Roman Zippel
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=20021101203546.C26989@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.org \
--cc=zippel@linux-m68k.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