From: honghui.zhang@mediatek.com (Honghui Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code
Date: Thu, 21 Dec 2017 10:13:23 +0800 [thread overview]
Message-ID: <1513822403.25872.3.camel@mhfsdcap03> (raw)
In-Reply-To: <1513822130-18213-1-git-send-email-honghui.zhang@mediatek.com>
On Thu, 2017-12-21 at 10:08 +0800, honghui.zhang at mediatek.com wrote:
> From: Honghui Zhang <honghui.zhang@mediatek.com>
>
> Two fixups for mediatek's host bridge:
> The first patch fixup the IRQ handle routine to avoid IRQ reentry which
> may exist for both MT2712 and MT7622.
> The second patch fixup class type for MT7622.
>
Sorry about the noise, to the wrong mail group, please ignore this.
thanks.
> Change Since v1:
> - Add the second patch.
> - Make the first patch's commit message more standard.
>
> Honghui Zhang (2):
> PCI: mediatek: Clear IRQ status after IRQ dispatched to avoid reentry
> PCI: mediatek: Fixup class type for MT7622
>
> drivers/pci/host/pcie-mediatek.c | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2017-12-21 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 2:08 [PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code honghui.zhang at mediatek.com
2017-12-21 2:08 ` [PATCH v2 1/2] PCI: mediatek: Clear IRQ status after IRQ dispatched to avoid reentry honghui.zhang at mediatek.com
2017-12-21 2:08 ` [PATCH v2 2/2] PCI: mediatek: Fixup class type for MT7622 honghui.zhang at mediatek.com
2017-12-21 2:13 ` Honghui Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-21 2:11 [PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code honghui.zhang at mediatek.com
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=1513822403.25872.3.camel@mhfsdcap03 \
--to=honghui.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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