All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <gregkh@linuxfoundation.org>, <rafael.j.wysocki@intel.com>,
	<linux-cxl@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH 1/3] driver core: faux: Suppress bind attributes
Date: Mon, 9 Jun 2025 11:19:57 +0100	[thread overview]
Message-ID: <20250609111957.00003c07@huawei.com> (raw)
In-Reply-To: <20250607033228.1475625-2-dan.j.williams@intel.com>

On Fri, 6 Jun 2025 20:32:26 -0700
Dan Williams <dan.j.williams@intel.com> wrote:

> faux_device_create() is almost a suitable candidate to replace
> platform_driver_probe() if not for the fact that faux_device_create()
> supports dynamic attach/detach of the driver.
> 
> Drop the bind attributes with the expectation that simple faux devices can
> always assume that the device is permanently bound at create, and only
> unbound at 'destroy'.
> 
> The acpi-einj driver depends on static bind.
> 
> Fixes: 6cb9441bfe8d ("ACPI: APEI: EINJ: Transition to the faux device interface")
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Cc: Danilo Krummrich <dakr@kernel.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Seems like a fair assumption that these should never be used so
we might as well hide the.

Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

> ---
>  drivers/base/faux.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/base/faux.c b/drivers/base/faux.c
> index 9054d346bd7f..934da77ca48b 100644
> --- a/drivers/base/faux.c
> +++ b/drivers/base/faux.c
> @@ -86,6 +86,7 @@ static struct device_driver faux_driver = {
>  	.name		= "faux_driver",
>  	.bus		= &faux_bus_type,
>  	.probe_type	= PROBE_FORCE_SYNCHRONOUS,
> +	.suppress_bind_attrs = true,
>  };
>  
>  static void faux_device_release(struct device *dev)


  reply	other threads:[~2025-06-09 10:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  3:32 [PATCH 0/3] CXL: ACPI: faux: Fix cxl_core.ko module load regression Dan Williams
2025-06-07  3:32 ` [PATCH 1/3] driver core: faux: Suppress bind attributes Dan Williams
2025-06-09 10:19   ` Jonathan Cameron [this message]
2025-06-07  3:32 ` [PATCH 2/3] driver core: faux: Quiet probe failures Dan Williams
2025-06-09 10:19   ` Jonathan Cameron
2025-06-07  3:32 ` [PATCH 3/3] ACPI: APEI: EINJ: Do not fail einj_init() on faux_device_create() failure Dan Williams
2025-06-09 10:17   ` Jonathan Cameron
2025-06-09 10:42     ` Greg KH
2025-06-09 16:05       ` Jonathan Cameron
2025-06-10 17:22         ` Dan Williams
2025-06-09 13:28   ` Cheatham, Benjamin
2025-06-09 13:39 ` [PATCH 0/3] CXL: ACPI: faux: Fix cxl_core.ko module load regression Sudeep Holla
2025-06-09 15:04 ` Dave Jiang
2025-06-09 18:58   ` Rafael J. Wysocki
2025-06-10 10:12     ` Greg KH
2025-06-10 17:24       ` Rafael J. Wysocki

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=20250609111957.00003c07@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=dakr@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.