From: Andrew Lunn <andrew@lunn.ch>
To: afzal mohammed <afzal.mohd.ma@gmail.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Gregory Clement <gregory.clement@bootlin.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v3] ARM: orion: replace setup_irq() by request_irq()
Date: Sun, 1 Mar 2020 16:44:35 +0100 [thread overview]
Message-ID: <20200301154435.GJ6305@lunn.ch> (raw)
In-Reply-To: <20200301122330.4296-1-afzal.mohd.ma@gmail.com>
On Sun, Mar 01, 2020 at 05:53:30PM +0530, afzal mohammed wrote:
> request_irq() is preferred over setup_irq(). Invocations of setup_irq()
> occur after memory allocators are ready.
>
> Per tglx[1], setup_irq() existed in olden days when allocators were not
> ready by the time early interrupts were initialized.
>
> Hence replace setup_irq() by request_irq().
>
> [1] https://lkml.kernel.org/r/alpine.DEB.2.20.1710191609480.1971@nanos
>
> Signed-off-by: afzal mohammed <afzal.mohd.ma@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
_______________________________________________
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-01 15:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 12:23 [PATCH v3] ARM: orion: replace setup_irq() by request_irq() afzal mohammed
2020-03-01 15:44 ` Andrew Lunn [this message]
2020-03-08 14:37 ` afzal mohammed
2020-03-09 16:17 ` Gregory CLEMENT
2020-03-13 20:39 ` Gregory CLEMENT
-- strict thread matches above, loose matches on Subject: below --
2020-03-01 12:23 [PATCH v3] ARM: spear: " afzal mohammed
2020-03-02 3:17 ` Viresh Kumar
2020-03-01 12:22 [PATCH v3] ARM: mmp: " afzal mohammed
2020-03-08 14:53 ` afzal mohammed
[not found] ` <20200308161903.GA156645@furthur.local>
2020-03-01 12:22 ` [PATCH v3] ARM: iop32x: " afzal mohammed
2020-03-09 12:19 ` [PATCH v3] ARM: mmp: " afzal mohammed
2020-03-01 12:21 [PATCH v3] ARM: ep93xx: Replace " afzal mohammed
2020-03-01 16:21 ` Alexander Sverdlin
2020-03-01 12:19 [PATCH v3] ARM: OMAP: replace " afzal mohammed
2020-03-04 16:34 ` Tony Lindgren
2020-03-13 15:45 ` [PATCH v3] ARM: " afzal mohammed
2020-03-17 4:37 ` afzal mohammed
2020-03-25 11:43 ` afzal mohammed
2020-03-27 10:46 ` afzal mohammed
2020-03-27 10:55 ` Arnd Bergmann
2020-03-27 11:10 ` afzal mohammed
2020-03-27 11:29 ` afzal mohammed
2020-03-27 11:58 ` Arnd Bergmann
2020-03-27 12:41 ` [PATCH v4 1/5] ARM: ep93xx: Replace " afzal mohammed
2020-03-27 12:44 ` [PATCH v4 2/5] ARM: spear: replace " afzal mohammed
2020-03-27 12:44 ` [PATCH v4 3/5] ARM: cns3xxx: " afzal mohammed
2020-03-27 12:44 ` [PATCH v4 4/5] ARM: mmp: " afzal mohammed
2020-03-27 12:44 ` [PATCH v4 5/5] ARM: iop32x: " afzal mohammed
2020-03-27 12:53 ` [PATCH v3] ARM: " afzal mohammed
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=20200301154435.GJ6305@lunn.ch \
--to=andrew@lunn.ch \
--cc=afzal.mohd.ma@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sebastian.hesselbarth@gmail.com \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).