public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net: drop pointless static qualifier in atl2_probe()
Date: Tue, 19 Feb 2019 14:34:33 +0000	[thread overview]
Message-ID: <20190219143433.GJ17104@kadam> (raw)
In-Reply-To: <20190219143252.134824-1-maowenan@huawei.com>

On Tue, Feb 19, 2019 at 10:32:52PM +0800, Mao Wenan wrote:
> There is no need to have the 'T *v' variable static
> since new value always be assigned before use it.
> 
> Signed-off-by: Mao Wenan <maowenan@huawei.com>
> ---
>  drivers/net/ethernet/atheros/atlx/atl2.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/net/ethernet/atheros/atlx/atl2.c b/drivers/net/ethernet/atheros/atlx/atl2.c
> index bb41becb6609..6bd686b26837 100644
> --- a/drivers/net/ethernet/atheros/atlx/atl2.c
> +++ b/drivers/net/ethernet/atheros/atlx/atl2.c
> @@ -1335,13 +1335,11 @@ static int atl2_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>  {
>  	struct net_device *netdev;
>  	struct atl2_adapter *adapter;
> -	static int cards_found;
> +	int cards_found = 0;
>  	unsigned long mmio_start;
>  	int mmio_len;
>  	int err;
>  
> -	cards_found = 0;

You're sending patches too quickly and you're not thinking about what
you're doing.   If someone asks you to redo a patch, that should take
over night to accomplish when you take time to think about what you're
doing, but you have sent several versions of a patch in the same day.

This one is obviously wrong, but please take some time and slow down
before resending.

regards,
dan carpenter

  parent reply	other threads:[~2019-02-19 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 14:32 [PATCH] net: drop pointless static qualifier in atl2_probe() Mao Wenan
2019-02-19 14:33 ` Mao Wenan
2019-02-19 14:34 ` Dan Carpenter [this message]
2019-02-19 14:36 ` Dan Carpenter
2019-02-22  3:17 ` maowenan

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=20190219143433.GJ17104@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox