mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karsten Graul <kgraul@linux.ibm.com>
To: YueHaibing <yuehaibing@huawei.com>,
	ubraun@linux.ibm.com, davem@davemloft.net, kuba@kernel.org
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/smc: remove unused inline function smc_curs_read
Date: Wed, 29 Apr 2020 17:15:55 +0200	[thread overview]
Message-ID: <039d6d59-5dd5-c89a-c174-72f4de3d0098@linux.ibm.com> (raw)
In-Reply-To: <20200429132623.48608-1-yuehaibing@huawei.com>

On 29/04/2020 15:26, YueHaibing wrote:
> commit bac6de7b6370 ("net/smc: eliminate cursor read and write calls")
> left behind this.
> 

Thanks, good catch. Your patch will be part of our next patch submission.

Regards, Karsten


> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
>  net/smc/smc_cdc.h | 17 -----------------
>  1 file changed, 17 deletions(-)
> 
> diff --git a/net/smc/smc_cdc.h b/net/smc/smc_cdc.h
> index 861dc24c588c..5a19e5e2280e 100644
> --- a/net/smc/smc_cdc.h
> +++ b/net/smc/smc_cdc.h
> @@ -97,23 +97,6 @@ static inline void smc_curs_add(int size, union smc_host_cursor *curs,
>  	}
>  }
>  
> -/* SMC cursors are 8 bytes long and require atomic reading and writing */
> -static inline u64 smc_curs_read(union smc_host_cursor *curs,
> -				struct smc_connection *conn)
> -{
> -#ifndef KERNEL_HAS_ATOMIC64
> -	unsigned long flags;
> -	u64 ret;
> -
> -	spin_lock_irqsave(&conn->acurs_lock, flags);
> -	ret = curs->acurs;
> -	spin_unlock_irqrestore(&conn->acurs_lock, flags);
> -	return ret;
> -#else
> -	return atomic64_read(&curs->acurs);
> -#endif
> -}
> -
>  /* Copy cursor src into tgt */
>  static inline void smc_curs_copy(union smc_host_cursor *tgt,
>  				 union smc_host_cursor *src,
> 

      reply	other threads:[~2020-04-29 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 13:26 YueHaibing
2020-04-29 15:15 ` Karsten Graul [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=039d6d59-5dd5-c89a-c174-72f4de3d0098@linux.ibm.com \
    --to=kgraul@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ubraun@linux.ibm.com \
    --cc=yuehaibing@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®