From: James Smart <jsmart2021@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Marc Zyngier <maz@kernel.org>,
James Smart <james.smart@broadcom.com>,
Dick Kennedy <dick.kennedy@broadcom.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [patch 03/10] scsi: lpfc: Remove linux/msi.h include
Date: Sun, 13 Nov 2022 21:39:42 -0800 [thread overview]
Message-ID: <a15fbbb9-1f1e-c368-267d-5bcad5ce41c6@gmail.com> (raw)
In-Reply-To: <20221113202428.436270297@linutronix.de>
On 11/13/2022 12:33 PM, Thomas Gleixner wrote:
> Nothing in this file needs anything from linux/msi.h
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: James Smart <james.smart@broadcom.com>
> Cc: Dick Kennedy <dick.kennedy@broadcom.com>
> Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> Cc: linux-scsi@vger.kernel.org
> ---
> drivers/scsi/lpfc/lpfc_init.c | 1 -
> 1 file changed, 1 deletion(-)
>
> --- a/drivers/scsi/lpfc/lpfc_init.c
> +++ b/drivers/scsi/lpfc/lpfc_init.c
> @@ -36,7 +36,6 @@
> #include <linux/firmware.h>
> #include <linux/miscdevice.h>
> #include <linux/percpu.h>
> -#include <linux/msi.h>
> #include <linux/irq.h>
> #include <linux/bitops.h>
> #include <linux/crash_dump.h>
>
yep - agree.
Reviewed-by: James Smart <jsmart2021@gmail.com>
-- james
next prev parent reply other threads:[~2022-11-14 5:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 20:33 [patch 00/10] genirq/msi: Treewide cleanup of pointless linux/msi.h includes Thomas Gleixner
2022-11-13 20:33 ` [patch 01/10] mfd: timberdale: Remove linux/msi.h include Thomas Gleixner
2022-11-14 9:01 ` Lee Jones
2022-11-13 20:33 ` [patch 02/10] ata: ahci: " Thomas Gleixner
2022-11-13 23:29 ` Damien Le Moal
2022-11-13 20:33 ` [patch 03/10] scsi: lpfc: " Thomas Gleixner
2022-11-14 5:39 ` James Smart [this message]
2022-11-17 18:20 ` Martin K. Petersen
2022-11-13 20:34 ` [patch 04/10] bus: fsl-mc: Remove linux/msi.h includes Thomas Gleixner
2022-11-23 22:11 ` [tip: irq/core] " tip-bot2 for Thomas Gleixner
2022-11-13 20:34 ` [patch 05/10] dmaengine: idxd: Remove linux/msi.h include Thomas Gleixner
2022-11-13 22:29 ` Vinod Koul
2022-11-13 20:34 ` [patch 06/10] net: dpaa2: Remove linux/msi.h includes Thomas Gleixner
2022-11-13 20:34 ` [patch 07/10] net: nfp: " Thomas Gleixner
2022-11-14 10:46 ` Simon Horman
2022-11-13 20:34 ` [patch 08/10] soc: fsl: dpio: Remove linux/msi.h include Thomas Gleixner
2022-11-23 22:11 ` [tip: irq/core] " tip-bot2 for Thomas Gleixner
2022-11-13 20:34 ` [patch 09/10] vfio/fsl-mc: " Thomas Gleixner
2022-11-15 20:44 ` Jason Gunthorpe
2022-11-15 22:00 ` Alex Williamson
2022-11-23 22:11 ` [tip: irq/core] " tip-bot2 for Thomas Gleixner
2022-11-13 20:34 ` [patch 10/10] iommu/of: " Thomas Gleixner
2022-11-14 11:01 ` Robin Murphy
2022-11-23 22:11 ` [tip: irq/core] " tip-bot2 for Thomas Gleixner
2022-11-15 3:00 ` [patch 00/10] genirq/msi: Treewide cleanup of pointless linux/msi.h includes patchwork-bot+netdevbpf
2022-11-26 3:27 ` 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=a15fbbb9-1f1e-c368-267d-5bcad5ce41c6@gmail.com \
--to=jsmart2021@gmail.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
/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