public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] wait_on_bit: add an acquire memory barrier
Date: Sat, 1 Oct 2022 09:01:51 +0200	[thread overview]
Message-ID: <Yzfl3yCpo3eq2UIj@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.02.2209301134350.23900@file01.intranet.prod.int.rdu2.redhat.com>

On Fri, Sep 30, 2022 at 11:34:55AM -0400, Mikulas Patocka wrote:
> This is backport of the upstream patch 8238b4579866b7c1bb99883cfe102a43db5506ff
> for the stable branch 4.9
> 
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>

Again, you lost all of the original changelog and authorship/review
information here :(

And what order are these to be applied in?  Please make a patch series
for each stable/LTS tree they are to be backported to.  Would you want
to try to unwind this if you were the reciever of these emails?

thanks,

greg k-h

  reply	other threads:[~2022-10-01  7:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 15:32 backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Mikulas Patocka
2022-09-30 15:33 ` [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-09-30 15:33 ` Mikulas Patocka
2022-09-30 15:34 ` Mikulas Patocka
2022-09-30 15:34 ` Mikulas Patocka
2022-09-30 15:34 ` Mikulas Patocka
2022-10-01  7:01   ` Greg KH [this message]
2022-09-30 15:35 ` [PATCH] provide arch_test_bit_acquire for architectures that define test_bit Mikulas Patocka
2022-09-30 15:35 ` Mikulas Patocka
2022-09-30 15:36 ` Mikulas Patocka
2022-09-30 15:36 ` Mikulas Patocka
2022-09-30 15:36 ` Mikulas Patocka
2022-10-01  7:00   ` Greg KH
2022-10-01  6:59 ` backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Greg KH
2022-10-03 12:28   ` Mikulas Patocka
2022-10-03 12:28     ` [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-10-03 12:29     ` Mikulas Patocka
2022-10-03 12:29     ` Mikulas Patocka
2022-10-03 12:29     ` Mikulas Patocka
2022-10-03 12:30     ` Mikulas Patocka
2022-10-03 12:30     ` [PATCH] provide arch_test_bit_acquire for architectures that define test_bit Mikulas Patocka
2022-10-03 12:31     ` Mikulas Patocka
2022-10-03 12:31     ` Mikulas Patocka
2022-10-03 12:31     ` Mikulas Patocka
2022-10-03 12:32     ` Mikulas Patocka
2022-10-05 16:48     ` backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Greg KH
2022-10-10 19:08       ` Greg KH
2022-10-11  9:48         ` Mikulas Patocka
2022-10-11  9:58           ` Greg KH
2022-10-18 11:36             ` Mikulas Patocka
2022-10-18 11:37               ` [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-10-18 11:37               ` Mikulas Patocka
2022-10-18 11:38               ` Mikulas Patocka
2022-10-18 11:38               ` Mikulas Patocka
2022-10-18 11:39               ` Mikulas Patocka
2022-10-18 11:39               ` Mikulas Patocka
2022-10-18 11:39               ` Mikulas Patocka
2022-10-26 17:01               ` backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Greg KH
2022-10-27 11:45                 ` Mikulas Patocka
2022-10-27 11:53                   ` Greg KH
2022-10-27 12:48                     ` Mikulas Patocka

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=Yzfl3yCpo3eq2UIj@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=mpatocka@redhat.com \
    --cc=stable@vger.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