mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Duncan <lduncan@suse.com>
To: Xie XiuQi <xiexiuqi@huawei.com>,
	<QLogic-Storage-Upstream@cavium.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: qedi: remove unused variable udev & uctrl
Date: Tue, 5 May 2020 08:28:57 -0700	[thread overview]
Message-ID: <b4b7073d-be1f-ac6f-5fe2-b2a45ad2dec4@suse.com> (raw)
In-Reply-To: <20200505121904.25702-1-xiexiuqi@huawei.com>

On 5/5/20 5:19 AM, Xie XiuQi wrote:
> uctrl and udev are unused after commit 9632a6b4b747
> ("scsi: qedi: Move LL2 producer index processing in BH.")
> 
> Remove them.
> 
> Signed-off-by: Xie XiuQi <xiexiuqi@huawei.com>
> ---
>  drivers/scsi/qedi/qedi_main.c | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/drivers/scsi/qedi/qedi_main.c b/drivers/scsi/qedi/qedi_main.c
> index b995b19865ca..313f7e10aed9 100644
> --- a/drivers/scsi/qedi/qedi_main.c
> +++ b/drivers/scsi/qedi/qedi_main.c
> @@ -658,8 +658,6 @@ static struct qedi_ctx *qedi_host_alloc(struct pci_dev *pdev)
>  static int qedi_ll2_rx(void *cookie, struct sk_buff *skb, u32 arg1, u32 arg2)
>  {
>  	struct qedi_ctx *qedi = (struct qedi_ctx *)cookie;
> -	struct qedi_uio_dev *udev;
> -	struct qedi_uio_ctrl *uctrl;
>  	struct skb_work_list *work;
>  	struct ethhdr *eh;
>  
> @@ -698,9 +696,6 @@ static int qedi_ll2_rx(void *cookie, struct sk_buff *skb, u32 arg1, u32 arg2)
>  		  "Allowed frame ethertype [0x%x] len [0x%x].\n",
>  		  eh->h_proto, skb->len);
>  
> -	udev = qedi->udev;
> -	uctrl = udev->uctrl;
> -
>  	work = kzalloc(sizeof(*work), GFP_ATOMIC);
>  	if (!work) {
>  		QEDI_WARN(&qedi->dbg_ctx,
> 

Reviewed-by: Lee Duncan <lduncan@suse.com>

-- 
Lee


  reply	other threads:[~2020-05-05 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 12:19 Xie XiuQi
2020-05-05 15:28 ` Lee Duncan [this message]
2020-05-12  3:28 ` 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=b4b7073d-be1f-ac6f-5fe2-b2a45ad2dec4@suse.com \
    --to=lduncan@suse.com \
    --cc=QLogic-Storage-Upstream@cavium.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=xiexiuqi@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

all inboxes | Powered by JetHome®