From: afzal mohammed <afzal.mohd.ma@gmail•com>
To: maobibo <maobibo@loongson•cn>
Cc: linux-arm-kernel@lists•infradead.org,
Thomas Bogendoerfer <tsbogend@alpha•franken.de>,
Paul Burton <paulburton@kernel•org>,
linux-kernel@vger•kernel.org, Ralf Baechle <ralf@linux-mips•org>,
linux-mips@vger•kernel.org,
Florian Fainelli <f.fainelli@gmail•com>,
bcm-kernel-feedback-list@broadcom•com,
Jiaxun Yang <jiaxun.yang@flygoat•com>,
"Maciej W. Rozycki" <macro@linux-mips•org>,
John Crispin <john@phrozen•org>, Huacai Chen <chenhc@lemote•com>,
Nathan Chancellor <natechancellor@gmail•com>,
Keguang Zhang <keguang.zhang@gmail•com>,
Guenter Roeck <linux@roeck-us•net>
Subject: Re: [PATCH v4] MIPS: Replace setup_irq() by request_irq()
Date: Sat, 14 Mar 2020 12:19:48 +0530 [thread overview]
Message-ID: <20200314064948.GA5285@afzalpc> (raw)
In-Reply-To: <0b41aa60-9869-ab62-4c8e-cbf7c62cdb7e@loongson.cn>
On Sat, Mar 14, 2020 at 01:21:19PM +0800, maobibo wrote:
> yeap, this supplementary patch fixes the issue, and it works for my on my
> loongson64 RS780 machine.
Thanks, i will be sending a (hopefully) better patch based on the
feedback from Thomas.
Regards
afzal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-14 6:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 0:55 [PATCH v3] MIPS: Replace setup_irq() by request_irq() afzal mohammed
2020-03-04 20:31 ` Thomas Bogendoerfer
2020-03-05 11:57 ` [PATCH v4] " afzal mohammed
2020-03-06 12:47 ` Thomas Bogendoerfer
2020-03-11 5:31 ` Nathan Chancellor
2020-03-11 7:56 ` afzal mohammed
2020-03-11 9:03 ` afzal mohammed
2020-03-11 10:42 ` Thomas Bogendoerfer
2020-03-11 13:12 ` afzal mohammed
2020-03-11 16:03 ` Thomas Bogendoerfer
2020-03-11 16:32 ` afzal mohammed
2020-03-13 12:11 ` afzal mohammed
2020-03-14 8:13 ` [PATCH v2] MIPS: pass non-NULL dev_id on shared request_irq() afzal mohammed
2020-03-14 17:19 ` Guenter Roeck
2020-03-15 7:11 ` Nathan Chancellor
2020-03-16 15:32 ` Thomas Bogendoerfer
2020-03-14 6:55 ` [PATCH v4] MIPS: Replace setup_irq() by request_irq() afzal mohammed
2020-03-11 15:27 ` [PATCH] MIPS: pass non-NULL dev_id on shared request_irq() afzal mohammed
2020-03-11 16:06 ` afzal mohammed
2020-03-13 16:47 ` [PATCH v4] MIPS: Replace setup_irq() by request_irq() Guenter Roeck
2020-03-14 1:07 ` afzal mohammed
2020-03-14 5:21 ` maobibo
2020-03-14 6:49 ` afzal mohammed [this message]
2020-03-14 10:28 ` Guenter Roeck
2020-03-14 11:42 ` afzal mohammed
2020-03-05 12:29 ` [PATCH v3] " afzal mohammed
2020-03-05 12:42 ` afzal mohammed
2020-03-04 20:38 ` kbuild test robot
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=20200314064948.GA5285@afzalpc \
--to=afzal.mohd.ma@gmail$(echo .)com \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=chenhc@lemote$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=jiaxun.yang@flygoat$(echo .)com \
--cc=john@phrozen$(echo .)org \
--cc=keguang.zhang@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=macro@linux-mips$(echo .)org \
--cc=maobibo@loongson$(echo .)cn \
--cc=natechancellor@gmail$(echo .)com \
--cc=paulburton@kernel$(echo .)org \
--cc=ralf@linux-mips$(echo .)org \
--cc=tsbogend@alpha$(echo .)franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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