From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: anil.gurumurthy@qlogic.com, sudarsana.kalluru@qlogic.com,
James.Bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] scsi: bfa: Remove deadcode
Date: Tue, 15 Oct 2024 21:48:04 +0000 [thread overview]
Message-ID: <Zw7jFFSzcSPfln2Y@gallifrey> (raw)
In-Reply-To: <yq1ttddqdbh.fsf@ca-mkp.ca.oracle.com>
* Martin K. Petersen (martin.petersen@oracle.com) wrote:
>
> > This removes a pile of dead functions in the SCSI bfa driver.
> > These were spotted by hunting for unused symbols in a unmodular
> > kernel build, and then double checking by grepping for the function
> > name.
>
> Applied to 6.13/scsi-staging, thanks!
Thanks!
Dave
>
> --
> Martin K. Petersen Oracle Linux Engineering
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2024-10-15 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 12:56 [PATCH 0/5] scsi: bfa: Remove deadcode linux
2024-09-15 12:56 ` [PATCH 1/5] scsi: bfa: Remove unused bfa_core code linux
2024-09-15 12:56 ` [PATCH 2/5] scsi: bfa: Remove unused bfa_svc code linux
2024-09-15 12:56 ` [PATCH 3/5] scsi: bfa: Remove unused bfa_ioc code linux
2024-09-15 12:56 ` [PATCH 4/5] scsi: bfa: Remove unused bfa_fcs code linux
2024-09-15 12:56 ` [PATCH 5/5] scsi: bfa: Remove unused misc code linux
2024-10-15 14:22 ` [PATCH 0/5] scsi: bfa: Remove deadcode Dr. David Alan Gilbert
2024-10-15 21:14 ` Martin K. Petersen
2024-10-15 21:48 ` Dr. David Alan Gilbert [this message]
2024-10-26 1:37 ` 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=Zw7jFFSzcSPfln2Y@gallifrey \
--to=linux@treblig.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=anil.gurumurthy@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sudarsana.kalluru@qlogic.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