All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Manivannan Sadhasivam via B4 Relay"
	<devnull+manivannan.sadhasivam.oss.qualcomm.com@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 6/9] power: sequencing: Add an API to return the pwrseq device's 'dev' pointer
Date: Tue, 19 May 2026 10:45:52 +0000	[thread overview]
Message-ID: <20260519104553.5E9DDC2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519-pwrseq-m2-bt-v3-6-b39dc2ae3966@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing kernel-doc comment explaining the lifetime of the device pointer returned by pwrseq_to_device().
--

commit d29f3508bf71a5cf1f39e83cf08db650ff869721
Author: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>

power: sequencing: Add an API to return the pwrseq device's 'dev' pointer

This commit adds an API to return the pwrseq device's dev pointer to
consumers, allowing them to query the provider's DT node.

> diff --git a/drivers/power/sequencing/core.c b/drivers/power/sequencing/core.c
> index 4dff71be11b60..96ad557297f5b 100644
> --- a/drivers/power/sequencing/core.c
> +++ b/drivers/power/sequencing/core.c
> @@ -965,6 +965,15 @@ int pwrseq_power_off(struct pwrseq_desc *desc)
>  }
>  EXPORT_SYMBOL_GPL(pwrseq_power_off);
>  
> +struct device *pwrseq_to_device(struct pwrseq_desc *desc)

This isn't a bug, but would it be useful to add a kernel-doc comment here
explaining the lifetime of the returned device pointer?

Since this function returns a non-refcounted pointer to the provider's struct
device, its lifetime is tied strictly to the pwrseq_desc object.

> +{
> +	if (!desc)
> +		return NULL;
> +
> +	return &desc->pwrseq->dev;
> +}
> +EXPORT_SYMBOL_GPL(pwrseq_to_device);

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260519-pwrseq-m2-bt-v3-0-b39dc2ae3966@oss.qualcomm.com?part=6

  reply	other threads:[~2026-05-19 10:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  8:55 [PATCH v3 0/9] Fixes/improvements for the PCI M.2 power sequencing driver Manivannan Sadhasivam
2026-05-19  8:55 ` Manivannan Sadhasivam via B4 Relay
2026-05-19  8:55 ` [PATCH v3 1/9] power: sequencing: pcie-m2: Fix inconsistent function prefixes Manivannan Sadhasivam
2026-05-19  8:55   ` Manivannan Sadhasivam via B4 Relay
2026-05-19 13:16   ` Fixes/improvements for the PCI M.2 power sequencing driver bluez.test.bot
2026-05-19  8:55 ` [PATCH v3 2/9] power: sequencing: pcie-m2: Allow creating serdev for multiple PCI devices Manivannan Sadhasivam
2026-05-19  8:55   ` Manivannan Sadhasivam via B4 Relay
2026-05-19  9:40   ` sashiko-bot
2026-05-19  8:55 ` [PATCH v3 3/9] power: sequencing: pcie-m2: Improve PCI device ID check Manivannan Sadhasivam
2026-05-19  8:55   ` Manivannan Sadhasivam via B4 Relay
2026-05-19  8:55 ` [PATCH v3 4/9] power: sequencing: pcie-m2: Create serdev for PCI devices present before probe Manivannan Sadhasivam
2026-05-19  8:55   ` Manivannan Sadhasivam via B4 Relay
2026-05-19 10:04   ` sashiko-bot
2026-05-19  8:56 ` [PATCH v3 5/9] power: sequencing: pcie-m2: Create BT node based on the pci_device_id[] table Manivannan Sadhasivam
2026-05-19  8:56   ` Manivannan Sadhasivam via B4 Relay
2026-05-19  8:56 ` [PATCH v3 6/9] power: sequencing: Add an API to return the pwrseq device's 'dev' pointer Manivannan Sadhasivam
2026-05-19  8:56   ` Manivannan Sadhasivam via B4 Relay
2026-05-19 10:45   ` sashiko-bot [this message]
2026-05-19  8:56 ` [PATCH v3 7/9] Bluetooth: hci_qca: Add M.2 Bluetooth device support using pwrseq Manivannan Sadhasivam
2026-05-19  8:56   ` Manivannan Sadhasivam via B4 Relay
2026-05-19 11:30   ` sashiko-bot
2026-05-19  8:56 ` [PATCH v3 8/9] Bluetooth: hci_qca: Rename 'power_ctrl_enabled' to 'bt_en_available' Manivannan Sadhasivam
2026-05-19  8:56   ` Manivannan Sadhasivam via B4 Relay
2026-05-19  8:56 ` [PATCH v3 9/9] Bluetooth: hci_qca: Set 'bt_en_available' based on W_DISABLE2# presence in M.2 connector Manivannan Sadhasivam
2026-05-19  8:56   ` Manivannan Sadhasivam via B4 Relay

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=20260519104553.5E9DDC2BCB3@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=devnull+manivannan.sadhasivam.oss.qualcomm.com@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.