From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3] mbuf/ip_frag: Move mbuf chaining to common code Date: Tue, 13 Oct 2015 15:17:51 +0200 Message-ID: <4024979.4xpSavg4hL@xps13> References: <20150831144110.4a7afa27@miho> <20150907145009.43cb1634@miho> <20151013145000.0bcf1c48@miho> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Simon Kagstrom Return-path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id CAF2F5A53 for ; Tue, 13 Oct 2015 15:18:58 +0200 (CEST) Received: by wicgb1 with SMTP id gb1so89211328wic.1 for ; Tue, 13 Oct 2015 06:18:58 -0700 (PDT) In-Reply-To: <20151013145000.0bcf1c48@miho> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-10-13 14:50, Simon Kagstrom: > Ping? OK you apply the ping method we have just talked about :) To make it really effective, you should have these headers: To: Olivier Matz Cc: dev@dpdk.org Indeed, as the mbuf maintainer, he's the target of your ping. And to make it clear, the title should be mbuf: move chaining from ip_frag library (note the lowercase in "move") Now you know how to do it so you can spread the word when someone forget these advices. Thanks