All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: "tangbin@cmss.chinamobile.com" <tangbin@cmss.chinamobile.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"leon@kernel.org" <leon@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/mlx5e: Use IS_ERR() to check and simplify code
Date: Fri, 15 May 2020 22:28:22 +0000	[thread overview]
Message-ID: <295e31680acd83c4f66b9f928f1cab7e77e97529.camel@mellanox.com> (raw)
In-Reply-To: <febc1254-ad7f-f564-6607-9ac89f1fcf40@cmss.chinamobile.com>

On Wed, 2020-05-13 at 17:48 +0800, Tang Bin wrote:
> Hi David:
> 
> On 2020/5/8 4:18, David Miller wrote:
> > From: Tang Bin <tangbin@cmss.chinamobile.com>
> > Date: Thu,  7 May 2020 19:50:10 +0800
> > 
> > > Use IS_ERR() and PTR_ERR() instead of PTR_ZRR_OR_ZERO()
                                            ^^^^^^^ typo
> > > to simplify code, avoid redundant judgements.
> > > 
> > > Signed-off-by: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
> > > Signed-off-by: Tang Bin <tangbin@cmss.chinamobile.com>
> > Saeed, please pick this up.
> 
> Does this mean the patch has been received and I just have to wait?
> 

no, mlx5 patches normally go to net-next-mlx5 branch and usually
pulled into net-next once a week when i send my pull requests.

i will reply with "applied" when i apply this patch,
but for now please fix the typo.

Thanks,
Saeed


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 11:50 [PATCH] net/mlx5e: Use IS_ERR() to check and simplify code Tang Bin
2020-05-07 13:40 ` Leon Romanovsky
2020-05-07 20:18 ` David Miller
2020-05-13  9:48   ` Tang Bin
2020-05-15 22:28     ` Saeed Mahameed [this message]
2020-05-15 22:54       ` Tang Bin

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=295e31680acd83c4f66b9f928f1cab7e77e97529.camel@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tangbin@cmss.chinamobile.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.