linux-kernel - Re: drivers/staging/meilhaus build broken with ftrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <adamy6ceeig.fsf@cisco.com>
Date:	Thu, 06 Aug 2009 15:58:15 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Greg KH <gregkh@...e.de>, Matt Fleming <matt@...sole-pimps.org>,
	David Kiliani <mail@...idkiliani.de>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: drivers/staging/meilhaus build broken with ftrace


 > 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/