From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: jiale yao <19888972804@163.com>
Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Paul Barker" <paul@pbarker.dev>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Mitsuhiro Kimura" <mitsuhiro.kimura.kc@renesas.com>,
"Claudiu Beznea" <claudiu.beznea.uj@bp.renesas.com>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 6/7] net: ravb: fix resource teardown ordering
Date: Tue, 6 Oct 2026 19:08:33 +0300 [thread overview]
Message-ID: <01c2f59d-8e22-434a-9f5b-b69608c3eae2@omp.ru> (raw)
In-Reply-To: <222db01f.1264.1a101087434.Coremail.19888972804@163.com>
On 10/3/26 12:11 PM, jiale yao wrote:
[...]
>> On 9/30/26 4:53 AM, jiale yao wrote:
>>
>> [...]
>>
>>> Thanks for your review.
>>
>> Top-posting on the kernel MLs is a bad idea... :-)
>>
>>> You're right — I'll split this into two patches:
>>> One patch for the IRQ/netdev ordering issue.
>>> One patch for the runtime PM resume failure handling.
>>> I'll use --no-git-fallback next time, sorry for this.
>
> v3 in https://lore.kernel.org/all/20261003085940.493951-7-yaojiale02@163.com/
> It only addresses the IRQ/netdev teardown ordering issue. The runtime
> PM resume failure handling has been left unchanged.
Too bad you forgot to address Niklas' comment this time... :-)
> I plan to submit the runtime PM fix separately after the patch above
> has been applied, to avoid conflicts between the two changes, or any
> other suggestion?
Yeah, it seems a good idea to address the broken commits in the
chronological order... However, the fixes seem pretty much orthogonal
to each other?
[...]
MBR, Sergey
next prev parent reply other threads:[~2026-10-06 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 14:47 [PATCH v2 0/7] net: ethernet: release managed IRQs before freeing netdevs Jiale Yao
2026-09-27 14:47 ` [PATCH v2 1/7] net: macb: manage the netdev lifetime with devres Jiale Yao
2026-09-27 14:47 ` [PATCH v2 2/7] net: fec: " Jiale Yao
2026-09-28 2:57 ` Wei Fang
2026-09-27 14:47 ` [PATCH v2 3/7] net: hip04: " Jiale Yao
2026-09-30 3:48 ` netdev-bot+sashiko
2026-09-27 14:47 ` [PATCH v2 4/7] net: hisi_femac: " Jiale Yao
2026-09-27 14:47 ` [PATCH v2 5/7] net: hix5hd2: " Jiale Yao
2026-09-27 14:47 ` [PATCH v2 6/7] net: ravb: fix resource teardown ordering Jiale Yao
2026-09-27 16:01 ` Niklas Söderlund
2026-09-28 9:33 ` jiale yao
2026-09-29 19:07 ` Sergey Shtylyov
2026-09-30 1:53 ` jiale yao
2026-09-30 15:50 ` Sergey Shtylyov
2026-10-03 9:11 ` jiale yao
2026-10-06 16:08 ` Sergey Shtylyov [this message]
2026-09-30 3:49 ` netdev-bot+sashiko
2026-09-27 14:47 ` [PATCH v2 7/7] net: sxgbe: manage IRQ data lifetimes with devres Jiale Yao
2026-09-30 3:49 ` netdev-bot+sashiko
2026-09-27 22:30 ` [PATCH v2 0/7] net: ethernet: release managed IRQs before freeing netdevs Jakub Kicinski
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=01c2f59d-8e22-434a-9f5b-b69608c3eae2@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=19888972804@163.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mitsuhiro.kimura.kc@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=paul@pbarker.dev \
--cc=stable@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
all inboxes | Powered by JetHome®