All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Kees Cook <keescook@chromium.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	David Windsor <dwindsor@gmail.com>,
	"Reshetova, Elena" <elena.reshetova@intel.com>,
	Hans Liljestrand <ishkamiel@gmail.com>
Subject: Re: [tip:locking/core] refcount_t: Introduce a special purpose refcount type
Date: Mon, 13 Feb 2017 20:36:23 +0100	[thread overview]
Message-ID: <20170213193623.GA28747@gmail.com> (raw)
In-Reply-To: <20170213180020.GK6500@twins.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> wrote:

> > > And since size then isn't an issue what so ever anymore, remove the debug 
> > > knob and make all WARN()s unconditional.
> > 
> > Are you still going to land the x86 WARN_ON improvements?
> 
> Yes, once I manage to eke some response out of the relevant arch maintainers on 
> the subject ;-)

so I'm enthusiastically in support of it all! Does that count as a response? ;-)

Thanks,

	Ingo

  reply	other threads:[~2017-02-13 19:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-f405df5de3170c00e5c54f8b7cf4766044a032ba@git.kernel.org>
2017-02-13 14:34 ` [tip:locking/core] refcount_t: Introduce a special purpose refcount type Peter Zijlstra
2017-02-13 17:48   ` Kees Cook
2017-02-13 18:00     ` Peter Zijlstra
2017-02-13 19:36       ` Ingo Molnar [this message]
2017-02-13 20:13       ` Linus Torvalds
2017-02-14  7:29   ` Reshetova, Elena
2017-02-15  9:02     ` Ingo Molnar
2017-02-15 11:17       ` Reshetova, Elena

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=20170213193623.GA28747@gmail.com \
    --to=mingo@kernel.org \
    --cc=dwindsor@gmail.com \
    --cc=elena.reshetova@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=ishkamiel@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 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.