public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Waiman Long <longman@redhat.com>
Cc: john.p.donnelly@oracle.com,
	chenguanyou <chenguanyou9338@gmail.com>,
	dave@stgolabs.net, hdanton@sina.com,
	linux-kernel@vger.kernel.org, mazhenhua@xiaomi.com,
	mingo@redhat.com, peterz@infradead.org, quic_aiquny@quicinc.com,
	will@kernel.org, sashal@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v5] locking/rwsem: Make handoff bit handling more consistent
Date: Thu, 14 Apr 2022 12:48:19 +0200	[thread overview]
Message-ID: <Ylf78yGuXdXWugpn@kroah.com> (raw)
In-Reply-To: <b3620b7b-c66a-65f8-b10b-c3669b2f82ec@redhat.com>

On Tue, Apr 12, 2022 at 01:04:05PM -0400, Waiman Long wrote:
> The patch has already been in the tip tree. It may not be easy to add a
> Fixes tag to it. Anyway, I will encourage stable tree maintainer to take it
> as it does fix a problem as shown in your test.

I have no idea what you want me to do here.  Please be explicit...

thanks,

greg k-h

  reply	other threads:[~2022-04-14 10:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211116012912.723980-1-longman@redhat.com>
     [not found] ` <20220214154741.12399-1-chenguanyou@xiaomi.com>
     [not found]   ` <3f02975c-1a9d-be20-32cf-f1d8e3dfafcc@oracle.com>
     [not found]     ` <e873727e-22db-3330-015d-bd6581a2937a@redhat.com>
     [not found]       ` <31178c33-e25c-c3e8-35e2-776b5211200c@oracle.com>
     [not found]         ` <161c2e25-3d26-4dd7-d378-d1741f7bcca8@redhat.com>
     [not found]           ` <2b6ed542-b3e0-1a87-33ac-d52fc0e0339c@oracle.com>
2022-04-12 17:04             ` [PATCH v5] locking/rwsem: Make handoff bit handling more consistent Waiman Long
2022-04-14 10:48               ` Greg KH [this message]
2022-04-14 15:18                 ` Waiman Long
2022-04-14 15:42                   ` Greg KH
2022-04-14 15:44                     ` Waiman Long

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=Ylf78yGuXdXWugpn@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chenguanyou9338@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=hdanton@sina.com \
    --cc=john.p.donnelly@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mazhenhua@xiaomi.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=quic_aiquny@quicinc.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.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