From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jason Yan <yanaijie@huawei.com>,
satishkh@cisco.com, kartilak@cisco.com, sebaddel@cisco.com,
linux-scsi@vger.kernel.org, jejb@linux.ibm.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 0/4] scsi: fnic: build warnings clean up
Date: Tue, 8 Sep 2020 22:09:20 -0400 [thread overview]
Message-ID: <159961731708.5787.1672306758892214874.b4-ty@oracle.com> (raw)
In-Reply-To: <20200831081126.3251288-1-yanaijie@huawei.com>
On Mon, 31 Aug 2020 16:11:22 +0800, Jason Yan wrote:
> Some build warnings cleanup.
>
> Jason Yan (4):
> scsi: fnic: remove set but not used 'old_vlan'
> scsi: fnic: remove set but not used variable in
> is_fnic_fip_flogi_reject()
> scsi: fnic: remove set but not used 'fr_len'
> scsi: fnic: remove set but not used 'eth_hdrs_stripped'
>
> [...]
Applied to 5.10/scsi-queue, thanks!
[1/4] scsi: fnic: Remove set but not used 'old_vlan'
https://git.kernel.org/mkp/scsi/c/c65b4f37db46
[2/4] scsi: fnic: Remove set but not used variable in is_fnic_fip_flogi_reject()
https://git.kernel.org/mkp/scsi/c/6c53316d4898
[3/4] scsi: fnic: Remove set but not used 'fr_len'
https://git.kernel.org/mkp/scsi/c/446034e3d419
[4/4] scsi: fnic: Remove set but not used 'eth_hdrs_stripped'
https://git.kernel.org/mkp/scsi/c/16d7fd9079af
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-09-09 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 8:11 [PATCH 0/4] scsi: fnic: build warnings clean up Jason Yan
2020-08-31 8:11 ` [PATCH 1/4] scsi: fnic: remove set but not used 'old_vlan' Jason Yan
2020-08-31 8:11 ` [PATCH 2/4] scsi: fnic: remove set but not used variable in is_fnic_fip_flogi_reject() Jason Yan
2020-08-31 8:11 ` [PATCH 3/4] scsi: fnic: remove set but not used 'fr_len' Jason Yan
2020-08-31 8:11 ` [PATCH 4/4] scsi: fnic: remove set but not used 'eth_hdrs_stripped' Jason Yan
2020-09-09 2:09 ` Martin K. Petersen [this message]
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=159961731708.5787.1672306758892214874.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.com \
--cc=yanaijie@huawei.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).