From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: "DRI mailing list" <dri-devel@lists.freedesktop.org>,
linux-graphics-maintainer@vmware.com,
"Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Will Deacon" <will.deacon@arm.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Rik van Riel" <riel@surriel.com>,
"Minchan Kim" <minchan@kernel.org>,
"Michal Hocko" <mhocko@suse.com>,
"Huang Ying" <ying.huang@intel.com>,
"Souptick Joarder" <jrdr.linux@gmail.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
Linux-MM <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/3] mm: Allow the [page|pfn]_mkwrite callbacks to drop the mmap_sem
Date: Wed, 20 Mar 2019 10:44:25 -0700 [thread overview]
Message-ID: <CAADWXX9N+mCN5Vg1eVz9k-UFMQPzc5QXUm6fieBf0oEnC1-=OA@mail.gmail.com> (raw)
In-Reply-To: <20190320152315.82758-2-thellstrom@vmware.com>
On Wed, Mar 20, 2019 at 8:23 AM Thomas Hellstrom <thellstrom@vmware.com> wrote:
>
> Driver fault callbacks are allowed to drop the mmap_sem when expecting
> long hardware waits [...]
No comment on the patch itself, but please fix your email setup.
All the patches were marked as spam, because you sent them from your
vmware.com address, but without going through the proper vmware smtp
gateway.
So they lack the proper vmware DKIM hashes and proper mail handling
should (and does) consider them spam.
Linus
next prev parent reply other threads:[~2019-03-20 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 15:23 [RFC PATCH 0/3] mm modifications / helpers for emulated GPU coherent memory Thomas Hellstrom
2019-03-20 15:23 ` [RFC PATCH 1/3] mm: Allow the [page|pfn]_mkwrite callbacks to drop the mmap_sem Thomas Hellstrom
2019-03-20 17:44 ` Linus Torvalds [this message]
2019-03-20 15:23 ` [RFC PATCH 2/3] mm: Add an apply_to_pfn_range interface Thomas Hellstrom
2019-03-20 15:23 ` [RFC PATCH 3/3] mm: Add write-protect and clean utilities for address space ranges Thomas Hellstrom
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='CAADWXX9N+mCN5Vg1eVz9k-UFMQPzc5QXUm6fieBf0oEnC1-=OA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=thellstrom@vmware.com \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).