From: Marion & Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
jejb@linux.ibm.com, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] scsi: cumana_2: Fix different dev_id between 'request_irq()' and 'free_irq()'
Date: Sat, 30 May 2020 10:41:40 +0000 [thread overview]
Message-ID: <63fbba26-82f4-5c4b-90d6-d951eb914f50@wanadoo.fr> (raw)
In-Reply-To: <20200530094338.GE1551@shell.armlinux.org.uk>
Le 30/05/2020 à 11:43, Russell King - ARM Linux admin a écrit :
> On Sat, May 30, 2020 at 09:35:55AM +0200, Christophe JAILLET wrote:
>> The dev_id used in 'request_irq()' and 'free_irq()' should match.
>> So use 'host' in both cases.
>>
>> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> This is itself wrong. cumanascsi_2_intr() requires "info" as the devid.
> Either cumanascsi_2_intr() needs changing to use shost_priv(host) along
> with this change, or free_irq() needs changing to use "info".
My bad.
I've only looked at the difference of the dev_id for the 2 functions,
not at the usage of it with the function registered by 'request_irq'.
This one is obviously correct, or the driver would have some problems
somewhere.
I don't know why have chosen to change request_irq and not free_irq.
So obvious. I'm a little embarrassed and will send a v2.
Thx for the quick reply and review.
All the 3 patches being in "/drivers/scsi/arm/", do you prefer only 1
patch for the 3, or separated as I've done so far?
CJ
> Likely the same for the other patches, I haven't looked.
>
next prev parent reply other threads:[~2020-05-30 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 7:35 [PATCH] scsi: cumana_2: Fix different dev_id between 'request_irq()' and 'free_irq()' Christophe JAILLET
2020-05-30 9:43 ` Russell King - ARM Linux admin
2020-05-30 10:41 ` Marion & Christophe JAILLET [this message]
2020-06-25 20:47 ` Christophe JAILLET
2020-06-25 23:10 ` Russell King - ARM Linux admin
2020-06-27 3:09 ` Martin K. Petersen
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=63fbba26-82f4-5c4b-90d6-d951eb914f50@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.petersen@oracle.com \
/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).