From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758039AbcAMT4T (ORCPT ); Wed, 13 Jan 2016 14:56:19 -0500 Received: from shards.monkeyblade.net ([149.20.54.216]:36714 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932794AbcAMTx6 (ORCPT ); Wed, 13 Jan 2016 14:53:58 -0500 Date: Wed, 13 Jan 2016 14:53:54 -0500 (EST) Message-Id: <20160113.145354.1680040047047045639.davem@davemloft.net> To: gregory.clement@free-electrons.com Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, thomas.petazzoni@free-electrons.com, f.fainelli@gmail.com, jason@lakedaemon.net, andrew@lunn.ch, sebastian.hesselbarth@gmail.com, linux-arm-kernel@lists.infradead.org, alior@marvell.com, nadavh@marvell.com, mw@semihalf.com, simon.guinot@sequanux.org, ezequiel.garcia@free-electrons.com, maxime.ripard@free-electrons.com, boris.brezillon@free-electrons.com, linux@arm.linux.org.uk, w@1wt.eu, arnd@arndb.de Subject: Re: [PATCH net-next 00/10] Proposal for a API set for HW Buffer management From: David Miller In-Reply-To: <87pox5wfd5.fsf@free-electrons.com> References: <1452625834-22166-1-git-send-email-gregory.clement@free-electrons.com> <20160112.155224.1322028826893670746.davem@davemloft.net> <87pox5wfd5.fsf@free-electrons.com> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 13 Jan 2016 11:53:57 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Gregory CLEMENT Date: Wed, 13 Jan 2016 18:36:54 +0100 > I perfectly understand that you are busy during this merge > window. However, I didn't expect a feedback from you but more from the > others who were involved previously on this topic. When a patch is submitted with "net-next" in the Subject line and no "RFC" or other indication like that, it means you think the patch is ready for me to consider applying to my tree. You have to communicate properly in your Subject line tags if you want me to interpret your changes one way or another. And quite frankly, I really don't even want to see a lot of RFC networking changes posted when the merge window is open, I only want to see bug fixes and people concentrating on that instead of future work. Thanks.