All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: tglx@linutronix.de, hpa@zytor.com, peterz@infradead.org,
	mingo@kernel.org, prsood@codeaurora.org,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:locking/core] locking/osq_lock: Fix osq_lock queue corruption
Date: Thu, 31 Aug 2017 12:40:19 -0700	[thread overview]
Message-ID: <20170831194019.GB2408@linux-80c1.suse> (raw)
In-Reply-To: <tip-50972fe78f24f1cd0b9d7bbf1f87d2be9e4f412e@git.kernel.org>

On Thu, 10 Aug 2017, tip-bot for Prateek Sood wrote:

>Signed-off-by: Prateek Sood <prsood@codeaurora.org>
>[ Added pictures, rewrote comments. ]
>Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>Cc: Linus Torvalds <torvalds@linux-foundation.org>
>Cc: Peter Zijlstra <peterz@infradead.org>
>Cc: Thomas Gleixner <tglx@linutronix.de>
>Cc: sramana@codeaurora.org
>Link: http://lkml.kernel.org/r/1500040076-27626-1-git-send-email-prsood@codeaurora.org
>Signed-off-by: Ingo Molnar <mingo@kernel.org>

Any reason -stable wasn't Cc'ed here? This goes back to 3.15:

fb0527bd5ea (locking/mutexes: Introduce cancelable MCS lock for adaptive spinning)

Thanks,
Davidlohr

  reply	other threads:[~2017-08-31 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 13:47 [PATCH] osq_lock: fix osq_lock queue corruption Prateek Sood
2017-07-18 11:25 ` Peter Zijlstra
2017-08-10 12:11 ` [tip:locking/core] locking/osq_lock: Fix " tip-bot for Prateek Sood
2017-08-31 19:40   ` Davidlohr Bueso [this message]
2017-09-01 11:17     ` Peter Zijlstra
2017-09-01 14:22       ` Davidlohr Bueso

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=20170831194019.GB2408@linux-80c1.suse \
    --to=dave@stgolabs.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=prsood@codeaurora.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.