From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?U2ltb24gS8OlZ3N0csO2bQ==?= Subject: Small request for patch review in DPDK Date: Wed, 27 May 2015 07:59:25 +0200 Message-ID: <55655D3D.8070208@netinsight.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: dev@dpdk.org Return-path: Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.21]) by dpdk.org (Postfix) with SMTP id 436533B5 for ; Wed, 27 May 2015 07:59:29 +0200 (CEST) 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" Hi! As a well-meaning outsider submitting small patches to DPDK, I'd very much appreciate help from the community with review and comments. Since I'm a DPDK newbie, the patches might be incorrect or wrong in some other way, so I think it's even more important with reviews for people like me. But I can't help getting this nagging feeling that the patches are actually lost in the flood of mail to the DPDK mailing list, since I haven't gotten any reaction to any of the three patches I've sent the last month. The patches in question are kni: Add set_rx_mode callback to handle multicast groups rte_reorder: Allow sequence numbers > 0 as starting point eal_common_options: Allow combining -m and --no-huge so if someone feels like mining their DPDK mail box, please review if you have the time and knowledge about the area :-) And I can't help thinking that maybe github pull requests would be harder to miss (or at least easier to find after a few weeks of other traffic). // Simon