From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: cgel.zte@gmail.com
Cc: chi.minghao@zte.com.cn, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, s.shtylyov@omp.ru,
zealci@zte.com.cn
Subject: Re: [PATCH V3] ata: pata_pxa: Use platform_get_irq() to get the interrupt
Date: Thu, 10 Mar 2022 11:21:37 +0900 [thread overview]
Message-ID: <268d5589-fb80-b1d8-a513-69530ca2ab9e@opensource.wdc.com> (raw)
In-Reply-To: <20220309072834.2081944-1-chi.minghao@zte.com.cn>
On 3/9/22 16:28, cgel.zte@gmail.com wrote:
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
> allocation of IRQ resources in DT core code, this causes an issue
> when using hierarchical interrupt domains using "interrupts" property
> in the node as this bypasses the hierarchical setup and messes up the
> irq chaining.
>
> In preparation for removal of static setup of IRQ resource from DT core
> code use platform_get_irq().
>
> v1->v2:
> - Use more specific in the subject: ata: pata_pxa:
> - Switch to returning 'irq'
> v2->v3:
> - drop the unlikely()
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
Applied to for-5.18 (without commit message fix). Thanks !
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2022-03-10 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 5:50 [PATCH V2] " cgel.zte
2022-03-09 6:24 ` Damien Le Moal
2022-03-09 7:28 ` [PATCH V3] " cgel.zte
2022-03-09 7:31 ` Damien Le Moal
2022-03-09 8:55 ` Sergei Shtylyov
2022-03-09 9:00 ` Sergey Shtylyov
2022-03-09 8:51 ` Sergey Shtylyov
2022-03-10 2:21 ` Damien Le Moal [this message]
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=268d5589-fb80-b1d8-a513-69530ca2ab9e@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=zealci@zte.com.cn \
/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®