From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] update sn2_defconfig to include new console
Date: Sun, 18 Jul 2004 19:57:40 +0000 [thread overview]
Message-ID: <200407181557.40248.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200407171704.08219.jbarnes@engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Sunday, July 18, 2004 3:34 pm, Jesse Barnes wrote:
> On Saturday, July 17, 2004 7:24 pm, Keith Owens wrote:
> > On Sat, 17 Jul 2004 17:04:08 -0400,
> >
> > Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> > >===== arch/ia64/configs/sn2_defconfig 1.8 vs edited =====
> > >--- 1.8/arch/ia64/configs/sn2_defconfig 2004-06-24 06:42:21 -07:00
> > >+++ edited/arch/ia64/configs/sn2_defconfig 2004-07-17 09:24:59 -07:00
> > >@@ -24,6 +24,7 @@
> > > # CONFIG_EMBEDDED is not set
> > > CONFIG_KALLSYMS=y
> > > CONFIG_KALLSYMS_ALL=y
> > >+CONFIG_KALLSYMS_EXTRA_PASS=y
> >
> > CONFIG_KALLSYMS_EXTRA_PASS should not be turned on by default. It is
> > only to be used when there is a bug in the kallsyms code, the extra
> > pass provides debugging data and lets the users continue to build while
> > we work out what is wrong with kallsyms.
>
> Oh, I see. I thought it was a 'double check' against bad values. I'll
> send out another update shortly that turns it off.
Here it is, live from Ottawa.
Jesse
[-- Attachment #2: sn2-defconfig-console-2.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2004-07-18 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 21:04 [PATCH] update sn2_defconfig to include new console Jesse Barnes
2004-07-17 23:24 ` Keith Owens
2004-07-18 19:34 ` Jesse Barnes
2004-07-18 19:57 ` Jesse Barnes [this message]
2004-07-18 20:15 ` Jesse Barnes
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=200407181557.40248.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.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