Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: "davem@davemloft.net" <davem@davemloft.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"hslester96@gmail.com" <hslester96@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"leon@kernel.org" <leon@kernel.org>
Subject: Re: [PATCH v2] net/mlx5e: Use refcount_t for refcount
Date: Tue, 6 Aug 2019 21:25:55 +0000	[thread overview]
Message-ID: <bd5df8d6fc9ed2be710dbca06739b7b580a309cc.camel@mellanox.com> (raw)
In-Reply-To: <20190806.134848.2232719643712591918.davem@davemloft.net>

On Tue, 2019-08-06 at 13:48 -0700, David Miller wrote:
> From: Saeed Mahameed <saeedm@mellanox.com>
> Date: Tue, 6 Aug 2019 20:42:56 +0000
> 
> > On Sat, 2019-08-03 at 00:48 +0800, Chuhong Yuan wrote:
> > > refcount_t is better for reference counters since its
> > > implementation can prevent overflows.
> > > So convert atomic_t ref counters to refcount_t.
> > > 
> > > Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> > > ---
> > > Changes in v2:
> > >   - Add #include.
> > > 
> > 
> > Acked-by: Saeed Mahameed <saeedm@mellanox.com>
> > 
> > Dave, up to you take it, or leave it to me :).
> 
> Please take it, thank you.

Ok, running some build tests will apply shortly to net-next-mlx5.
Thanks everyone!

      reply	other threads:[~2019-08-06 21:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 16:48 [PATCH v2] net/mlx5e: Use refcount_t for refcount Chuhong Yuan
2019-08-04 12:58 ` Leon Romanovsky
2019-08-04 14:44   ` Chuhong Yuan
2019-08-05  6:13     ` Leon Romanovsky
2019-08-05  6:55       ` Chuhong Yuan
2019-08-05 20:06         ` Saeed Mahameed
2019-08-06  6:59           ` Leon Romanovsky
2019-08-06 18:38             ` Jason Gunthorpe
2019-08-06 18:54               ` Saeed Mahameed
2019-08-06 20:42 ` Saeed Mahameed
2019-08-06 20:48   ` David Miller
2019-08-06 21:25     ` Saeed Mahameed [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=bd5df8d6fc9ed2be710dbca06739b7b580a309cc.camel@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=hslester96@gmail.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@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