From: Hangbin Liu <haliu@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>,
Phil Sutter <phil@nwl.cc>, Hangbin Liu <liuhangbin@gmail.com>
Subject: Re: [PATCHv4 iproute2 2/2] lib/libnetlink: update rtnl_talk to support malloc buff at run time
Date: Wed, 25 Oct 2017 21:16:12 +0800 [thread overview]
Message-ID: <20171025131612.GN29971@leo.usersys.redhat.com> (raw)
In-Reply-To: <20171025124556.14df7d15@shemminger-XPS-13-9360>
On Wed, Oct 25, 2017 at 12:45:56PM +0200, Stephen Hemminger wrote:
> This does not apply cleanly to net-next branch
>
> Applying: lib/libnetlink: update rtnl_talk to support malloc buff at run time
> error: patch failed: ip/ipl2tp.c:185
> error: ip/ipl2tp.c: patch does not apply
> error: patch failed: ip/iplink.c:1023
> error: ip/iplink.c: patch does not apply
> Patch failed at 0002 lib/libnetlink: update rtnl_talk to support malloc buff at run time
>
Oh, I will send a new version patch based on latest net-next code ASAP.
Thanks
Hangbin
prev parent reply other threads:[~2017-10-25 13:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 13:33 [PATCHv4 iproute2 0/2] libnetlink: malloc correct buff at run time Hangbin Liu
2017-09-28 13:33 ` [PATCHv4 iproute2 1/2] lib/libnetlink: re malloc buff if size is not enough Hangbin Liu
2017-09-29 12:55 ` Michal Kubecek
2017-09-29 17:54 ` Stephen Hemminger
2017-09-29 18:20 ` Michal Kubecek
2017-09-30 13:54 ` Hangbin Liu
2017-09-28 13:33 ` [PATCHv4 iproute2 2/2] lib/libnetlink: update rtnl_talk to support malloc buff at run time Hangbin Liu
2017-09-29 13:06 ` Michal Kubecek
2017-10-02 17:37 ` Stephen Hemminger
2017-10-09 20:25 ` Phil Sutter
2017-10-10 6:41 ` Michal Kubecek
2017-10-10 16:47 ` Stephen Hemminger
2017-10-11 10:40 ` Hangbin Liu
2017-10-11 11:10 ` Phil Sutter
2017-10-11 14:35 ` David Ahern
2017-10-12 16:07 ` Stephen Hemminger
2017-10-13 10:31 ` Phil Sutter
2017-10-25 10:45 ` Stephen Hemminger
2017-10-25 13:16 ` Hangbin Liu [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=20171025131612.GN29971@leo.usersys.redhat.com \
--to=haliu@redhat.com \
--cc=liuhangbin@gmail.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).