From: Steven Rostedt <rostedt@goodmis.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lihong.hi@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: + recordmcount-stfu.patch added to -mm tree
Date: Sat, 14 Nov 2009 00:33:42 -0500 [thread overview]
Message-ID: <1258176822.22249.239.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20091113212645.3956bc85.akpm@linux-foundation.org>
On Fri, 2009-11-13 at 21:26 -0800, Andrew Morton wrote:
> Dunno, really. How many people are running old objdump, and do we want
> to retard the rate at which the stragglers will upgrade?
I guess not, but by printing out a warning 1000000000000000000000000000
times per build, it may encourage them to upgrade ;-)
>
> I tend to be a late adopter ;) (for legit reasons, really - to catch
> things like this) so I'd be OK carrying that patch locally.
>
>
> Emitting that warning 1000000000000000000000000000 times per build is a
> bit obnoxious. Maybe find some way to restrict it to once per `make'?
>
I was originally going to do that, but then realized that he given patch
was easier to implement. I guess I can make a temp file that gets
deleted at the start of the build, and created the first time the
warning appears. Then the existence of that file will prevent other
warnings.
I'll play with this on Monday (if I remember ;-)
-- Steve
next prev parent reply other threads:[~2009-11-14 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200911140356.nAE3utfU001939@imap1.linux-foundation.org>
2009-11-14 4:58 ` Steven Rostedt
2009-11-14 5:26 ` Andrew Morton
2009-11-14 5:33 ` Steven Rostedt [this message]
2009-11-14 9:27 ` Ingo Molnar
2009-11-14 20:44 ` Steven Rostedt
2009-11-15 8:17 ` Ingo Molnar
2009-11-15 15:25 ` Steven Rostedt
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=1258176822.22249.239.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=lihong.hi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®