From: Kevin Hilman <khilman@baylibre.com>
To: s-vadapalli@ti.com
Cc: bhelgaas@google.com, j-keerthy@ti.com, kishon@kernel.org,
kw@linux.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-pci@vger.kernel.org, lpieralisi@kernel.org,
manivannan.sadhasivam@linaro.org, robh@kernel.org, srk@ti.com,
stable@vger.kernel.org, u-kumar1@ti.com, vigneshr@ti.com
Subject: Re: [PATCH 0/2] Fixes for the PCI dra7xx driver
Date: Fri, 30 Aug 2024 12:50:30 -0700 [thread overview]
Message-ID: <20240830195030.3586919-1-khilman@baylibre.com> (raw)
In-Reply-To: <20240827122422.985547-1-s-vadapalli@ti.com>
> This series is based on commit
> 3e9bff3bbe13 Merge tag 'vfs-6.11-rc6.fixes' of gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs
> of Mainline Linux.
>
> The first patch fixes conversion to "devm_request_threaded_irq()" where
> the IRQF_ONESHOT flag should have been added since the handler is NULL.
>
> The second patch fixes the error handling when IRQ request fails in the
> probe function. The existing error handling doesn't cleanup the changes
> performed prior to the IRQ request invocation.
I tested this patch on v6.11-rc5 using a am57xx-beagle-x15 with a SATA
drive connected to the eSATA port, and confirm that this allows
booting again.
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
Kevin
next prev parent reply other threads:[~2024-08-30 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 12:24 [PATCH 0/2] Fixes for the PCI dra7xx driver Siddharth Vadapalli
2024-08-27 12:24 ` [PATCH 1/2] PCI: dra7xx: Fix threaded IRQ request for "dra7xx-pcie-main" IRQ Siddharth Vadapalli
2024-09-02 7:33 ` Manivannan Sadhasivam
2024-08-27 12:24 ` [PATCH 2/2] PCI: dra7xx: Fix error handling when IRQ request fails in probe Siddharth Vadapalli
2024-08-27 14:00 ` Kumar, Udit
2024-09-02 7:40 ` Manivannan Sadhasivam
2024-08-30 19:50 ` Kevin Hilman [this message]
2024-09-13 22:51 ` [PATCH 0/2] Fixes for the PCI dra7xx driver Krzysztof Wilczyński
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=20240830195030.3586919-1-khilman@baylibre.com \
--to=khilman@baylibre.com \
--cc=bhelgaas@google.com \
--cc=j-keerthy@ti.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=stable@vger.kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
/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