[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1501091100530.15299@pobox.suse.cz>
Date: Fri, 9 Jan 2015 11:03:35 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
linux-kernel@...r.kernel.org, live-patching@...r.kernel.org,
linux-next@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Subject: Re: livepatching tree for linux-next
On Wed, 7 Jan 2015, Andrew Morton wrote:
> > --- a/kernel/livepatch/core.c
> > +++ b/kernel/livepatch/core.c
> > @@ -911,6 +911,12 @@ static int klp_init(void)
> > {
> > int ret;
> >
> > + ret = klp_check_compiler_support();
> > + if (ret) {
> > + pr_info("Your compiler is too old; turning off.\n");
> > + return -EINVAL;
> > + }
> > +
>
> Looks reasonable.
I've applied it and pushed out.
> It's a shame we've never figured out a way to do this at Kconfig-time.
The biggest problems probably is: what if you supply different CC during
build? Then you'll have to invalidate all dependencies and restart the
whole dependency resolution. The same goes for cross-compilation I guess.
--
Jiri Kosina
SUSE Labs
--
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/
Powered by blists - more mailing lists