From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "Jiang, Dave" <dave.jiang@intel.com>
Subject: Re: [PATCH 1/5] cxl/acpi: Autoload driver for 'cxl_acpi' test devices
Date: Mon, 1 Aug 2022 19:24:00 +0000 [thread overview]
Message-ID: <682c23574f6385d10485c9d12f935b3dff925cd7.camel@intel.com> (raw)
In-Reply-To: <165853775783.2430596.13637998086505316619.stgit@dwillia2-xfh.jf.intel.com>
On Fri, 2022-07-22 at 17:55 -0700, Dan Williams wrote:
> In support of CXL unit tests in the ndctl project, arrange for the
> cxl_acpi driver to load in response to the registration of cxl_test
> devices.
>
> Reported-by: Dave Jiang <dave.jiang@intel.com>
> Tested-by: Dave Jiang <dave.jiang@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> drivers/cxl/acpi.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Looks good,
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
> diff --git a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
> index 64004eb672d0..eb436268b92c 100644
> --- a/drivers/cxl/acpi.c
> +++ b/drivers/cxl/acpi.c
> @@ -515,12 +515,19 @@ static const struct acpi_device_id
> cxl_acpi_ids[] = {
> };
> MODULE_DEVICE_TABLE(acpi, cxl_acpi_ids);
>
> +static const struct platform_device_id cxl_test_ids[] = {
> + { "cxl_acpi" },
> + { },
> +};
> +MODULE_DEVICE_TABLE(platform, cxl_test_ids);
> +
> static struct platform_driver cxl_acpi_driver = {
> .probe = cxl_acpi_probe,
> .driver = {
> .name = KBUILD_MODNAME,
> .acpi_match_table = cxl_acpi_ids,
> },
> + .id_table = cxl_test_ids,
> };
>
> module_platform_driver(cxl_acpi_driver);
>
next prev parent reply other threads:[~2022-08-01 19:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 0:55 [PATCH 0/5] CXL Region Provisioning Fixes Dan Williams
2022-07-23 0:55 ` [PATCH 1/5] cxl/acpi: Autoload driver for 'cxl_acpi' test devices Dan Williams
2022-08-01 19:24 ` Verma, Vishal L [this message]
2022-07-23 0:56 ` [PATCH 2/5] cxl/region: Delete 'region' attribute from root decoders Dan Williams
2022-08-01 19:32 ` Alison Schofield
2022-08-01 19:38 ` Verma, Vishal L
2022-08-01 19:40 ` Verma, Vishal L
2022-08-01 21:32 ` Dan Williams
2022-08-01 21:32 ` Dan Williams
2022-07-23 0:56 ` [PATCH 3/5] cxl/acpi: Minimize granularity for x1 interleaves Dan Williams
2022-08-01 19:35 ` Alison Schofield
2022-08-01 19:45 ` Verma, Vishal L
2022-08-01 21:34 ` Dan Williams
2022-08-02 15:56 ` Jonathan Cameron
2022-08-02 16:52 ` Jonathan Cameron
2022-08-02 17:33 ` Dan Williams
2022-08-03 16:00 ` Jonathan Cameron
2022-08-03 17:18 ` Dan Williams
2022-08-04 9:32 ` Jonathan Cameron
2022-07-23 0:56 ` [PATCH 4/5] cxl/region: Stop initializing interleave granularity Dan Williams
2022-08-01 19:41 ` Alison Schofield
2022-08-01 19:47 ` Verma, Vishal L
2022-07-23 0:56 ` [PATCH 5/5] cxl/region: Constrain region granularity scaling factor Dan Williams
2022-08-01 19:43 ` Alison Schofield
2022-08-01 20:55 ` Verma, Vishal L
2022-08-03 16:17 ` Jonathan Cameron
2022-08-04 16:33 ` Dan Williams
2022-08-04 17:57 ` Dan Williams
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=682c23574f6385d10485c9d12f935b3dff925cd7.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.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 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).