From: Jason Gunthorpe <jgg@ziepe.ca>
To: mpenttil@redhat.com, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
apopple@nvidia.com, jhubbard@nvidia.com, rcampbell@nvidia.com,
vbabka@suse.cz
Subject: Re: [PATCH v8] mm/hmm/test: use char dev with struct device to get device node
Date: Tue, 6 Sep 2022 20:13:29 -0300 [thread overview]
Message-ID: <YxfUGRA9q13V3+ja@ziepe.ca> (raw)
In-Reply-To: <20220826050631.25771-1-mpenttil@redhat.com>
On Fri, Aug 26, 2022 at 08:06:31AM +0300, mpenttil@redhat.com wrote:
> From: Mika Penttilä <mpenttil@redhat.com>
>
> HMM selftests use an in-kernel pseudo device to emulate device
> memory. The pseudo device registers a major device range for two or
> four pseudo device instances. User space has a script that
> reads /proc/devices in order to find the assigned major number,
> and sends that to mknod(1), once for each node.
>
> Change this to properly use cdev and struct device APIs.
>
> Delete the /proc/devices parsing from the user-space test script, now
> that it is unnecessary.
>
> Also, deleted an unused field in struct dmirror_device: devmem.
>
> Signed-off-by: Mika Penttilä <mpenttil@redhat.com>
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> Cc: Alistair Popple <apopple@nvidia.com>
> Cc: Ralph Campbell <rcampbell@nvidia.com>
> Cc: Vlastimil Babka <vbabka@suse.cz>
Andrew, this looks OK, can you pick it up?
Thanks,
Jason
prev parent reply other threads:[~2022-09-06 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 5:06 [PATCH v8] mm/hmm/test: use char dev with struct device to get device node mpenttil
2022-09-06 23:13 ` Jason Gunthorpe [this message]
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=YxfUGRA9q13V3+ja@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpenttil@redhat.com \
--cc=rcampbell@nvidia.com \
--cc=vbabka@suse.cz \
/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).