mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	<cgel.zte@gmail.com>
Cc: <chi.minghao@zte.com.cn>, <linux-ide@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <zealci@zte.com.cn>
Subject: Re: [PATCH V3] ata: pata_pxa: Use platform_get_irq() to get the interrupt
Date: Wed, 9 Mar 2022 12:00:03 +0300	[thread overview]
Message-ID: <45fa6cff-948f-93e0-388c-42da30e70efb@omp.ru> (raw)
In-Reply-To: <d4f60079-9a99-c8e6-4a3c-4c77597cc151@gmail.com>

On 09.03.2022 11:55, Sergei Shtylyov 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()
>>
>> Looks good. FYI, the changelog above should be placed under the "---"
>> after your Signed-off-by so that it does not stay as part of the commit
>> message. No need to resend, I will remove this when applying.
>>
>> Sergey,
>>
>> Review OK ?
> 
>     Yes.

    Ugh, replied from the wrong account. I had provided my Reviewed-by: tag 
already...

>     Although, strictly speaking, we still need to check for IRQ0 as well...

    The platform_get_irq() patch preventing IRQ0 hasn't landed still...

MBR, Sergey

  reply	other threads:[~2022-03-09  9:00 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 [this message]
2022-03-09  8:51     ` Sergey Shtylyov
2022-03-10  2:21     ` Damien Le Moal

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=45fa6cff-948f-93e0-388c-42da30e70efb@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=cgel.zte@gmail.com \
    --cc=chi.minghao@zte.com.cn \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergei.shtylyov@gmail.com \
    --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®