From: Roland Dreier <rdreier@cisco.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <gregkh@suse.de>, Matt Fleming <matt@console-pimps.org>,
David Kiliani <mail@davidkiliani.de>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: drivers/staging/meilhaus build broken with ftrace
Date: Thu, 06 Aug 2009 15:58:15 -0700 [thread overview]
Message-ID: <adamy6ceeig.fsf@cisco.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908061849260.2840@gandalf.stny.rr.com> (Steven Rostedt's message of "Thu, 6 Aug 2009 18:51:26 -0400 (EDT)")
> Now the question is, is this a crucial enough change to push for 31, or
> should we leave this for 32?
I would say yes, push it for 31, since a distro is most likely going to
want to enable staging drivers and ftrace, and will hit this build
breakage.
> This patch is small enough for 31, but to add a warning would require a
> little more code rework. I can queue this up for 31 and then have the
> warning ready for 32.
Sounds like a good plan. The warning will probably push someone to
figure out what the meilhaus code is really trying to do.
- R.
next prev parent reply other threads:[~2009-08-06 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 21:37 drivers/staging/meilhaus build broken with ftrace Roland Dreier
2009-08-06 21:46 ` Steven Rostedt
2009-08-06 22:29 ` Greg KH
2009-08-06 22:47 ` Steven Rostedt
2009-08-06 22:51 ` Steven Rostedt
2009-08-06 22:58 ` Roland Dreier [this message]
2009-08-06 23:32 ` Greg KH
2009-08-07 0:01 ` [GIT PULL][2.6.31] tracing: have recordmcount.pl handle a section with only weak functions Steven Rostedt
2009-08-07 6:50 ` Ingo Molnar
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=adamy6ceeig.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@davidkiliani.de \
--cc=matt@console-pimps.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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