[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140706123506.GA18204@amd.pavel.ucw.cz>
Date: Sun, 6 Jul 2014 14:35:06 +0200
From: Pavel Machek <pavel@....cz>
To: Jiri Kosina <jkosina@...e.cz>
Cc: Jiri Slaby <jslaby@...e.cz>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
linux-kernel@...r.kernel.org, tj@...nel.org, rostedt@...dmis.org,
mingo@...hat.com, akpm@...ux-foundation.org, andi@...stfloor.org,
paulmck@...ux.vnet.ibm.com, jirislaby@...il.com,
Vojtech Pavlik <vojtech@...e.cz>, Michael Matz <matz@...e.de>,
Udo Seidel <udoseidel@....de>
Subject: Re: [PATCH -repost 05/21] kgr: update Kconfig documentation
On Sat 2014-07-05 21:47:45, Jiri Kosina wrote:
> On Fri, 4 Jul 2014, Pavel Machek wrote:
>
> > > Hi, why do you believe so? But it is not so important, see below.
> >
> > Because it is quite hard to prepare the patch, and there's not really
> > enough documentation..? And given choice between "spend half an hour
> > preparing patch" and "just reboot", people compiling their own kernels
> > know what to do...
>
> I fail to see how "having the skills to compile my own kernel" and "being
> responsible for a datacenter that can't afford immediate reboot of all
> nodes" are connected in any way.
Parse error, or too much irony.
Anyway, I'd suggest the Kconfig test be something like "say N unless
you know how to prepare patch for running kernel, and plan to do
that".
And, since you seem to be targeting sysadmins with this, it would be
cool to have sysadmin-targeted documentation explaining what patches
are safe to apply with kgraft and what are not.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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