From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: New driver (large patch) question. Date: Wed, 02 Mar 2016 11:21:26 +0100 Message-ID: <2110917.95LWFiBeeK@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Stephen Hurd Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 4FA11902 for ; Wed, 2 Mar 2016 11:23:01 +0100 (CET) Received: by mail-wm0-f49.google.com with SMTP id p65so73022904wmp.1 for ; Wed, 02 Mar 2016 02:23:01 -0800 (PST) In-Reply-To: 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, 2016-03-01 19:56, Stephen Hurd: > I submitted a new driver on Friday, and it was rejected for being over 300k. > > The rejection email suggested contacing dev-owner@dpdk.org, which I did on > Monday with no reply. > > What's the process to submit patches larger than the mailing list size > limit? A patch has two lives: 1/ it must be reviewed and accepted 2/ it will stay in the git history for future reference Those 2 periods require the patch to be well explained, with a reasonnable scope and a human readable size. The primary rule to think about is to introduce only one feature per patch. So the size should be naturally small and the mailing list don't need to accept greater sizes. To make it short, please split your driver in several introduction steps.