From: Anand Moon <linux.amoon@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
linux-pci@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: PCI/pwrctrl: Propagate dev_err_probe return value
Date: Sun, 19 Oct 2025 15:49:28 +0530 [thread overview]
Message-ID: <CANAwSgQmpJGo1SYDOmDQ39Fx5UH3_v857qiJpVCcxqUK=_V0Gg@mail.gmail.com> (raw)
In-Reply-To: <e88cb990-bf11-40f7-9c71-b14614fe53bf@web.de>
Hi Markus,
On Sun, 19 Oct 2025 at 14:26, Markus Elfring <Markus.Elfring@web.de> wrote:
>
> >> How does this view fit to the commit ab81f2f79c683c94bac622aafafbe8232e547159
> >> ("PCI/pwrctrl: Fix double cleanup on devm_add_action_or_reset() failure")
> >> from 2025-08-13?
> >>
> > Thank you for your guidance. My previous understanding was incorrect.
>
> Will an adjusted software understanding influence further collateral evolutions?
>
I will try to be more correct and improve myself.
Sorry for the inconvenience,
> Regards,
> Markus
Thanks
-Anand
next prev parent reply other threads:[~2025-10-19 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 7:02 [PATCH v1] PCI/pwrctrl: Propagate dev_err_probe return value Anand Moon
2025-10-18 7:31 ` Christophe JAILLET
2025-10-18 16:05 ` [PATCH] " Markus Elfring
2025-10-19 8:16 ` Anand Moon
2025-10-19 8:56 ` Markus Elfring
2025-10-19 10:19 ` Anand Moon [this message]
2025-10-18 15:13 ` [PATCH] " Markus Elfring
2025-10-31 8:28 ` [PATCH v1] " Manivannan Sadhasivam
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='CANAwSgQmpJGo1SYDOmDQ39Fx5UH3_v857qiJpVCcxqUK=_V0Gg@mail.gmail.com' \
--to=linux.amoon@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=christophe.jaillet@wanadoo.fr \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marek.vasut+renesas@mailbox.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).