From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=2Osh+a7wfV8Ne2hqC+SODPuLzkHn4kJONtu3GdkjqYo=; b=lKwSyIDJtQVsppHrkYxi2HGfVaxd+LudyrqdBoZCjavFJPS25uS6FOXo6oUxqsWs2J LjH6iccytT2GP0rIN2j4DBL9YG0LPfHL0HNzhGzGsLDa7c7IZnnyc1rCfuLft9Br0N+W T53CGpcL1ksFe/lX48ke8ITlob76DuKCNeWIoghFhWJ5T3PbxOKywtH7xOqHtnIuUvk2 GEysTYOWzAtdu8UKcgkj/NHtu4eYTl4v0owh+SeUNHA+mn+GN/oEWxpDwUG0wBP2Y+KJ gr6Wcoi87aLLVevSzlYLTmY0NL2avNcEsj2ewqDw/zURDFi+G4Ja6vsglCdIwrqGY3eE DOrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding; bh=2Osh+a7wfV8Ne2hqC+SODPuLzkHn4kJONtu3GdkjqYo=; b=MRrBm2CMQLLiq2Wq3Yf+2Gc6KAr8hv4E/37iZ4T8m97veDCo+RuqGbRniVxOaqOZQL Mbxry9ZrbzAeBY0b1d9E1K+bfe1tjHex6cWtRqPeIofCjaxQoGVDsuax/BSHADDjh3s8 fGFq4GxICdN6NngxlrgSZ2TPlV13dUFWPh7F6a/wvrCq2MLL7rnYQ+rwtGyCzyFXXHKJ M+Qli0D3ZRTfEMZAd5Joi2OD+SDWQF/YEN846HJ6lGrJWh7/3HuYgMbfUtqIXQRmfhUl gbVHbBUjTUcFgmXxmpWDUOV1rP1cX6776rqi4e21QYrosErIH5aJUzd2TPNvHyBWFRVT u6yA== X-Gm-Message-State: AD7BkJLoYRnfHPhNbnqmwLxzGbumDLkWIPzzN+z49fhYx7E79d5uHpLxZaVsgh3wvUDT0nQ/ X-Received: by 10.194.94.229 with SMTP id df5mr29763639wjb.133.1456914181169; Wed, 02 Mar 2016 02:23:01 -0800 (PST) Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by smtp.gmail.com with ESMTPSA id i2sm35145685wje.22.2016.03.02.02.23.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2016 02:23:00 -0800 (PST) From: Thomas Monjalon To: Stephen Hurd Date: Wed, 02 Mar 2016 11:21:26 +0100 Message-ID: <2110917.95LWFiBeeK@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] New driver (large patch) question. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2016 10:23:01 -0000 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.