From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Himanshu Madhani <himanshu.madhani@qlogic.com>,
jbottomley@parallels.com, hch@lst.de
Cc: giridhar.malavali@qlogic.com, andrew.vasquez@qlogic.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2] qla2xxx: fix rwlock recursion
Date: Wed, 14 Oct 2015 09:53:20 -0700 [thread overview]
Message-ID: <561E8880.2060204@sandisk.com> (raw)
In-Reply-To: <1444838261-20990-3-git-send-email-himanshu.madhani@qlogic.com>
On 10/14/2015 08:57 AM, Himanshu Madhani wrote:
> -qla82xx_pci_set_crbwindow_2M(struct qla_hw_data *ha, ulong off_in,
> - void __iomem **off_out)
> +qla82xx_pci_set_crbwindow_2M(struct qla_hw_data *ha, ulong *off)
> {
Hello Himanshu,
Do you think it would be possible to keep the input and output offset as
separate arguments ? Something that is very unfortunate about this patch
is that it converts the qla82xx_pci_set_crbwindow_2M() function again
into a function that expects an unsigned long in *off and writes an I/O
memory address into *off. It is impossible to avoid that source code
does not trigger any sparse warning if such functions occur.
Thanks,
Bart.
next prev parent reply other threads:[~2015-10-14 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 15:57 [PATCH 0/2] qla2xxx: Patches for 4.3.0-rc5+ scsi "misc" branch Himanshu Madhani
2015-10-14 15:57 ` [PATCH 1/2] qla2xxx: Remove unavailable firmware files Himanshu Madhani
2015-10-14 23:33 ` Julian Calaby
2015-10-15 7:45 ` Hannes Reinecke
2015-10-14 15:57 ` [PATCH 2/2] qla2xxx: fix rwlock recursion Himanshu Madhani
2015-10-14 16:53 ` Bart Van Assche [this message]
2015-10-14 17:33 ` Bart Van Assche
2015-10-14 21:07 ` Himanshu Madhani
2015-10-26 20:34 ` Himanshu Madhani
2015-10-15 7:50 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2015-11-16 22:57 Xose Vazquez Perez
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=561E8880.2060204@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=andrew.vasquez@qlogic.com \
--cc=giridhar.malavali@qlogic.com \
--cc=hch@lst.de \
--cc=himanshu.madhani@qlogic.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.