From: David Miller <davem@davemloft.net>
To: martinbj2008@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 net-next] net: only check perm protocol when register proto
Date: Thu, 17 Sep 2015 21:03:22 -0700 (PDT) [thread overview]
Message-ID: <20150917.210322.516155583143848569.davem@davemloft.net> (raw)
In-Reply-To: <1442548805-5489-1-git-send-email-martinbj2008@gmail.com>
From: martinbj2008@gmail.com
Date: Fri, 18 Sep 2015 00:00:05 -0400
> From: Junwei Zhang <martinbj2008@gmail.com>
>
> The permanent protocol nodes are at the head of the list,
> So only need check all these nodes.
>
> No matter the new node is permanent or not,
> insert the new node after the last permanent protocol node,
>
> If the new node conflicts with existing permanent node,
> return error.
>
> Signed-off-by: Martin Zhang <martinbj2008@gmail.com>
> ---
> V2: Fix indentation
> rewrite statement
Applied, thanks.
prev parent reply other threads:[~2015-09-18 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 0:14 [PATCH V1 net-next] net: only check perm protocol when register proto martinbj2008
2015-09-17 23:20 ` David Miller
2015-09-18 4:00 ` [PATCH V2 " martinbj2008
2015-09-18 4:03 ` David Miller [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=20150917.210322.516155583143848569.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martinbj2008@gmail.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 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).