public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kevin Easton <kevin@guarana.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	David Miller <davem@davemloft.net>, Arnd Bergmann <arnd@arndb.de>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH jiffies] Avoid undefined behavior from signed overflow
Date: Sun, 4 Aug 2013 13:34:15 -0700	[thread overview]
Message-ID: <20130804203415.GR3836@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+55aFz2mLabJTjKffYcJfWycseNUS5F=vEzmorL7QZn7SnxLQ@mail.gmail.com>

On Sun, Aug 04, 2013 at 01:23:13PM -0700, Linus Torvalds wrote:
> On Sun, Aug 4, 2013 at 1:20 PM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> >
> > I have it queued up for 3.12, as you say, due to "-fno-strict-overflow".
> > But if you would rather have it sooner, please let me know and I will send
> > a pull request.
> 
> No, that's fine. As long as it's somewhere. 3.12 is better, rc4 is
> already getting too big for my taste.

3.12 it is, then!

							Thanx, Paul


      reply	other threads:[~2013-08-04 20:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 22:58 [PATCH jiffies] Avoid undefined behavior from signed overflow Paul E. McKenney
2013-07-28 18:46 ` Eric Dumazet
2013-07-29  2:55   ` Paul E. McKenney
2013-07-29  5:30 ` caf
2013-07-29 13:54   ` Paul E. McKenney
2013-07-29 14:01     ` Kevin Easton
2013-07-29 14:28       ` Paul E. McKenney
2013-08-04 19:16         ` Linus Torvalds
2013-08-04 20:20           ` Paul E. McKenney
2013-08-04 20:23             ` Linus Torvalds
2013-08-04 20:34               ` Paul E. McKenney [this message]

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=20130804203415.GR3836@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=john.stultz@linaro.org \
    --cc=kevin@guarana.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox