[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200314065548.GB5285@afzalpc>
Date: Sat, 14 Mar 2020 12:25:48 +0530
From: afzal mohammed <afzal.mohd.ma@...il.com>
To: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc: Nathan Chancellor <natechancellor@...il.com>,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Ralf Baechle <ralf@...ux-mips.org>,
Paul Burton <paulburton@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
bcm-kernel-feedback-list@...adcom.com,
"Maciej W. Rozycki" <macro@...ux-mips.org>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Keguang Zhang <keguang.zhang@...il.com>,
Huacai Chen <chenhc@...ote.com>,
John Crispin <john@...ozen.org>
Subject: Re: [PATCH v4] MIPS: Replace setup_irq() by request_irq()
Hi,
On Wed, Mar 11, 2020 at 10:02:49PM +0530, afzal mohammed wrote:
> On Wed, Mar 11, 2020 at 05:03:07PM +0100, Thomas Bogendoerfer wrote:
> > in your patch. How can we make sure they are unique enough for the use
> > case ? I guess using handler as dev_id does a better job here.
>
> There was one prior similar usage using string pointers, another way i
> have seen is using irq no. itself,
Huh, that was a total nonsense statement from me, considering the
expectation of a unique dev_id, i don't know what i was thinking at
that time, though you mentioned about uniqueness.
Regards
afzal
Powered by blists - more mailing lists