Note: the subject line should be [PATCH v3 3/9] ... instead of putting
v3 at the end of the subject line.
There are tools that parse the subject line and expect this convention.
See Documentation/process/submitting-patches.rst
Thanks.
On 4/27/19 8:01 AM, Thomas Hellstrom wrote:
Add two utilitie
Add two utilities to a) write-protect and b) clean all ptes pointing into
a range of an address space.
The utilities are intended to aid in tracking dirty pages (either
driver-allocated system memory or pci device memory).
The write-protect utility should be used in conjunction with
page_mkwrite()
Add two utilities to a) write-protect and b) clean all ptes pointing into
a range of an address space
The utilities are intended to aid in tracking dirty pages (either
driver-allocated system memory or pci device memory).
The write-protect utility should be used in conjunction with
page_mkwrite() a
On 4/12/19 9:04 AM, Thomas Hellstrom wrote:
Add two utilities to a) write-protect and b) clean all ptes pointing into
a range of an address space
A period at the end, please.
The utilities are intended to aid in tracking dirty pages (either
driver-allocated system memory or pci device memory
Hi, Ralph,
On Fri, 2019-04-12 at 11:52 -0700, Ralph Campbell wrote:
> On 4/12/19 9:04 AM, Thomas Hellstrom wrote:
> > Add two utilities to a) write-protect and b) clean all ptes
> > pointing into
> > a range of an address space
>
> A period at the end, please.
>
> > The utilities are intended to
Add two utilities to a) write-protect and b) clean all ptes pointing into
a range of an address space
The utilities are intended to aid in tracking dirty pages (either
driver-allocated system memory or pci device memory).
The write-protect utility should be used in conjunction with
page_mkwrite() a