From: davem@davemloft.net (David Miller)
Subject: [PATCH v3 0/2] sparc64: Add privileged ADI driver
Date: Fri, 20 Apr 2018 16:06:53 -0400 (EDT) [thread overview]
Message-ID: <20180420.160653.391583024671680574.davem@davemloft.net> (raw)
Message-ID: <20180420200653.N6nq_d2E_bcTZpcBosi8k18BpP8whdMYHruh1VJcPUo@z> (raw)
In-Reply-To: <20180420193939.487546-1-tom.hromatka@oracle.com>
Something put your commit message texts completely into the subject
lines of the patch emails.
Please fix this and resubmit as v4.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-20 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 19:39 [PATCH v3 0/2] sparc64: Add privileged ADI driver tom.hromatka
2018-04-20 19:39 ` Tom Hromatka
2018-04-20 19:39 ` [PATCH v3 1/2] SPARC M7 and newer processors utilize ADI to version and protect memory. This driver is capable of reading/writing ADI/MCD versions from privileged user space processes. Addresses in the adi file are mapped linearly to physical memory at a ratio of 1:adi_blksz. Thus, a read (or write) of offset K in the file operates upon the ADI version at physical address K * adi_blksz. The version information is encoded as one version per byte. Intended consumers are makedumpfile and crash tom.hromatka
2018-04-20 19:39 ` Tom Hromatka
2018-04-20 19:39 ` [PATCH v3 2/2] Add a selftest for the sparc64 privileged ADI driver. These tests verify the read(), pread(), write(), pwrite(), and seek() functionality of the driver. The tests also report simple performance statistics: tom.hromatka
2018-04-20 19:39 ` Tom Hromatka
2018-04-20 20:06 ` davem [this message]
2018-04-20 20:06 ` [PATCH v3 0/2] sparc64: Add privileged ADI driver David Miller
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=20180420.160653.391583024671680574.davem@davemloft.net \
--to=davem@davemloft.net \
/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).