All of lore.kernel.org
 help / color / mirror / Atom feed
From: "weiyongjun (A)" <weiyongjun1@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: "jiri@mellanox.com" <jiri@mellanox.com>,
	"arkadis@mellanox.com" <arkadis@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next] devlink: fix return value check in devlink_dpipe_header_put()
Date: Wed, 12 Apr 2017 03:30:25 +0000	[thread overview]
Message-ID: <6AADFAC011213A4C87B956458587ADB47B0128@SZXEMI508-MBX.china.huawei.com> (raw)
In-Reply-To: <20170411.230328.1122763321161603727.davem@davemloft.net>

Hi David,

> -----Original Message-----
> From: David Miller [mailto:davem@davemloft.net]
> Sent: Wednesday, April 12, 2017 11:03 AM
> To: weiyj.lk@gmail.com
> Cc: jiri@mellanox.com; arkadis@mellanox.com; weiyongjun (A)
> <weiyongjun1@huawei.com>; netdev@vger.kernel.org
> Subject: Re: [PATCH net-next] devlink: fix return value check in
> devlink_dpipe_header_put()
> 
> From: Wei Yongjun <weiyj.lk@gmail.com>
> Date: Mon, 10 Apr 2017 13:11:06 +0000
> 
> > From: Wei Yongjun <weiyongjun1@huawei.com>
> >
> > Fix the retrn value check which testing the wrong variable
> > in devlink_dpipe_header_put().
> >
> > Fixes: 1555d204e743 ("devlink: Support for pipeline debug (dpipe)")
> > Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> 
> This doesn't apply cleanly to net-next, please respin and also fix
> the typo in your commit message as pointed out by Jiri.

You have applied the v2 version of this patch some hours ago.  

Regards,
Yongjun Wei

  reply	other threads:[~2017-04-12  3:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 13:11 [PATCH net-next] devlink: fix return value check in devlink_dpipe_header_put() Wei Yongjun
2017-04-11  6:39 ` Jiri Pirko
2017-04-11 16:02 ` [PATCH net-next v2] " Wei Yongjun
2017-04-11 18:53   ` David Miller
2017-04-12  3:03 ` [PATCH net-next] " David Miller
2017-04-12  3:30   ` weiyongjun (A) [this message]
2017-04-12 14:19     ` David Miller

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=6AADFAC011213A4C87B956458587ADB47B0128@SZXEMI508-MBX.china.huawei.com \
    --to=weiyongjun1@huawei.com \
    --cc=arkadis@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=jiri@mellanox.com \
    --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 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.