public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: dedekind1@gmail.com
Cc: Valdis.Kletnieks@vt.edu, Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile
Date: Mon, 04 Apr 2011 17:01:02 +0100	[thread overview]
Message-ID: <4D99EB3E.1020202@grupopie.com> (raw)
In-Reply-To: <1301931464.2760.101.camel@localhost>

Artem Bityutskiy wrote:
> On Mon, 2011-04-04 at 11:22 -0400, Valdis.Kletnieks@vt.edu wrote:
>> [...]
>> When was the last time we actually saw such a bug report?  I'm suspecting that
>> all the affected people just set the variable and get on with their lives.  So
>> we should either just make it automatic if that's what people are going to do,
>> or we rip the entire "EXTRA_PASS' stuff out forcibly and *make* people fix the
>> actual underlying issue that causes the extra pass to be needed...
> 
> I do not know when this bug was last seen, but I'd not remove this
> "extra pass" work around so far. WRT automatic fix-up - I do not have
> strong opinion here, but Paulo Marques pointed in another thread that
> due to various alignment issues the bug is tricky and may come back. So
> probably removing working code is not very wise. Thus, it seems the way
> I proposed in this patch is a good balance.
> 
> But anyway, if Michal Marek requests to change this, I'll do this (he is
> the Maintainer).

Doing a search on a mail archive for "Inconsistent kallsyms data"
results in a dozen or so threads, and the last one seems to be on alpha
in 2008.

Not very frequent for certain, but not in the "never been seen" category
either.

-- 
Paulo Marques - www.grupopie.com

"All I ask is a chance to prove that money can't make me happy."

  reply	other threads:[~2011-04-04 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 10:40 [PATCH 1/2] Kconfig: improve KALLSYMS_ALL documentation Artem Bityutskiy
2011-04-04 10:40 ` [PATCH 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile Artem Bityutskiy
2011-04-04 12:17   ` Michal Marek
2011-04-04 12:48     ` Artem Bityutskiy
2011-04-04 12:45   ` Valdis.Kletnieks
2011-04-04 12:47     ` Artem Bityutskiy
2011-04-04 15:22       ` Valdis.Kletnieks
2011-04-04 15:37         ` Artem Bityutskiy
2011-04-04 16:01           ` Paulo Marques [this message]
2011-04-04 15:47     ` Artem Bityutskiy
2011-04-04 16:22 ` [PATCH 1/2] Kconfig: improve KALLSYMS_ALL documentation Randy Dunlap

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=4D99EB3E.1020202@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=dedekind1@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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