All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Hernberg <jhernberg@alchemy.lu>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin.
Date: Fri, 11 Dec 2015 20:47:20 +0100	[thread overview]
Message-ID: <20151211204720.3571ad93@balder.valhalla.alchemy.lu> (raw)
In-Reply-To: <20151211165240.GG6720@linutronix.de>

On Fri, 11 Dec 2015 17:52:40 +0100
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:

> * Joakim Hernberg | 2015-09-23 19:33:40 [+0200]:
> 
> >Since the HWLAT_DETECTOR driver supposedly shouldn't be builtin, but
> >a module when used at all, it would make sense to limit the
> >configuration choices:  
> 
> what is wrong with it beeing built-in? The default is m already.

To be quite honest I'm not quite sure anymore, think it fails when
built in.  I also faintly remember an irc discussion where it was
claimed that it shouldn't be built into the kernel, think that was the
reason for creating the patch.

-- 

   Joakim

  reply	other threads:[~2015-12-11 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 17:33 [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin Joakim Hernberg
2015-12-11 16:52 ` Sebastian Andrzej Siewior
2015-12-11 19:47   ` Joakim Hernberg [this message]
2015-12-13 10:39   ` Joakim Hernberg
2015-12-22 15:11     ` Sebastian Andrzej Siewior
2015-12-22 16:25       ` John Kacur
2015-12-22 16:34         ` Sebastian Andrzej Siewior
2015-12-22 16:43           ` John Kacur

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=20151211204720.3571ad93@balder.valhalla.alchemy.lu \
    --to=jhernberg@alchemy.lu \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.