From: Greg KH <gregkh@linuxfoundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: stable@vger.kernel.org, jannh@google.com,
torvalds@linux-foundation.org, vbabka@suse.cz, peterx@redhat.com,
aarcange@redhat.com, david@redhat.com, jgg@ziepe.ca,
ktkhai@virtuozzo.com, shli@fb.com, namit@vmware.com, hch@lst.de,
oleg@redhat.com, kirill@shutemov.name, jack@suse.cz,
willy@infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH 1/1] gup: document and work around "COW can break either way" issue
Date: Tue, 12 Oct 2021 12:06:21 +0200 [thread overview]
Message-ID: <YWVeHbWp3kqf7Hyj@kroah.com> (raw)
In-Reply-To: <20211012015244.693594-1-surenb@google.com>
On Mon, Oct 11, 2021 at 06:52:44PM -0700, Suren Baghdasaryan wrote:
> From: Linus Torvalds <torvalds@linux-foundation.org>
>
> From: Linus Torvalds <torvalds@linux-foundation.org>
>
> commit 17839856fd588f4ab6b789f482ed3ffd7c403e1f upstream.
Both backports now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2021-10-12 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 1:52 [PATCH 1/1] gup: document and work around "COW can break either way" issue Suren Baghdasaryan
2021-10-12 1:55 ` Suren Baghdasaryan
2021-10-12 5:45 ` Greg Kroah-Hartman
2021-10-12 8:06 ` Jan Kara
2021-10-12 8:14 ` Vlastimil Babka
2021-10-12 8:42 ` Greg KH
2021-10-12 18:57 ` Thadeu Lima de Souza Cascardo
2021-10-13 8:56 ` Greg KH
2021-10-12 10:06 ` Greg KH [this message]
2021-10-12 16:16 ` Suren Baghdasaryan
2021-10-13 21:58 ` John Hubbard
-- strict thread matches above, loose matches on Subject: below --
2021-10-12 1:53 Suren Baghdasaryan
2021-04-21 22:57 Suren Baghdasaryan
2021-04-21 22:56 Suren Baghdasaryan
2021-04-23 15:05 ` Greg KH
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=YWVeHbWp3kqf7Hyj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aarcange@redhat.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=kernel-team@android.com \
--cc=kirill@shutemov.name \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=namit@vmware.com \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=shli@fb.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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.