From mboxrd@z Thu Jan 1 00:00:00 1970 From: andrew@lunn.ch (Andrew Lunn) Date: Tue, 30 May 2017 15:27:35 +0200 Subject: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU In-Reply-To: <20170530125643.GQ22219@n2100.armlinux.org.uk> References: <1496135772-20694-1-git-send-email-thomas.petazzoni@free-electrons.com> <1496135772-20694-5-git-send-email-thomas.petazzoni@free-electrons.com> <20170530121907.GO22219@n2100.armlinux.org.uk> <20170530143350.6f8563c1@free-electrons.com> <20170530125643.GQ22219@n2100.armlinux.org.uk> Message-ID: <20170530132735.GA21646@lunn.ch> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > > Once again: patches not submitted to the mailing list simply don't > > exist. So if you continue to keep those huge stack of patches out of > > tree and don't submit your work more regularly, in fine-grained patches > > series, the situation we have today will continue to happen. > > Given the number of patch sets that I have, that is simply an > impossibility to do on a continual basis - I have close to 500 > patches, and there's simply no way to post that number of patches. So you don't expect to every have your 500 patches merged? What might help is that you ask for help getting them merged. I know of at least 4 groups of people interested in your devlink and 10G PHY code. If you handed those patches over to these people, i'm sure we could find somebody to post them to the list, deal with the feedback, etc, to get them merged. It just needs you to say it is O.K. for somebody to take patches from your git tree. You are great at writing new code, but terrible at getting it merged. So try to find somebody who you trust, who you can hand the patches over to, to do the merge work. Andrew From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU Date: Tue, 30 May 2017 15:27:35 +0200 Message-ID: <20170530132735.GA21646@lunn.ch> References: <1496135772-20694-1-git-send-email-thomas.petazzoni@free-electrons.com> <1496135772-20694-5-git-send-email-thomas.petazzoni@free-electrons.com> <20170530121907.GO22219@n2100.armlinux.org.uk> <20170530143350.6f8563c1@free-electrons.com> <20170530125643.GQ22219@n2100.armlinux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170530125643.GQ22219-l+eeeJia6m9URfEZ8mYm6t73F7V6hmMc@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Russell King - ARM Linux Cc: Thomas Petazzoni , Thomas Gleixner , Jason Cooper , Marc Zyngier , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring , Ian Campbell , Pawel Moll , Mark Rutland , Kumar Gala , Sebastian Hesselbarth , Gregory Clement , Yehuda Yitschak , Antoine Tenart , Nadav Haklai , Hanna Hawa , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org > > Once again: patches not submitted to the mailing list simply don't > > exist. So if you continue to keep those huge stack of patches out of > > tree and don't submit your work more regularly, in fine-grained patches > > series, the situation we have today will continue to happen. > > Given the number of patch sets that I have, that is simply an > impossibility to do on a continual basis - I have close to 500 > patches, and there's simply no way to post that number of patches. So you don't expect to every have your 500 patches merged? What might help is that you ask for help getting them merged. I know of at least 4 groups of people interested in your devlink and 10G PHY code. If you handed those patches over to these people, i'm sure we could find somebody to post them to the list, deal with the feedback, etc, to get them merged. It just needs you to say it is O.K. for somebody to take patches from your git tree. You are great at writing new code, but terrible at getting it merged. So try to find somebody who you trust, who you can hand the patches over to, to do the merge work. Andrew -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751551AbdE3N1u (ORCPT ); Tue, 30 May 2017 09:27:50 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:58090 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751119AbdE3N1q (ORCPT ); Tue, 30 May 2017 09:27:46 -0400 Date: Tue, 30 May 2017 15:27:35 +0200 From: Andrew Lunn To: Russell King - ARM Linux Cc: Thomas Petazzoni , Thomas Gleixner , Jason Cooper , Marc Zyngier , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Rob Herring , Ian Campbell , Pawel Moll , Mark Rutland , Kumar Gala , Sebastian Hesselbarth , Gregory Clement , Yehuda Yitschak , Antoine Tenart , Nadav Haklai , Hanna Hawa , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU Message-ID: <20170530132735.GA21646@lunn.ch> References: <1496135772-20694-1-git-send-email-thomas.petazzoni@free-electrons.com> <1496135772-20694-5-git-send-email-thomas.petazzoni@free-electrons.com> <20170530121907.GO22219@n2100.armlinux.org.uk> <20170530143350.6f8563c1@free-electrons.com> <20170530125643.GQ22219@n2100.armlinux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170530125643.GQ22219@n2100.armlinux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Once again: patches not submitted to the mailing list simply don't > > exist. So if you continue to keep those huge stack of patches out of > > tree and don't submit your work more regularly, in fine-grained patches > > series, the situation we have today will continue to happen. > > Given the number of patch sets that I have, that is simply an > impossibility to do on a continual basis - I have close to 500 > patches, and there's simply no way to post that number of patches. So you don't expect to every have your 500 patches merged? What might help is that you ask for help getting them merged. I know of at least 4 groups of people interested in your devlink and 10G PHY code. If you handed those patches over to these people, i'm sure we could find somebody to post them to the list, deal with the feedback, etc, to get them merged. It just needs you to say it is O.K. for somebody to take patches from your git tree. You are great at writing new code, but terrible at getting it merged. So try to find somebody who you trust, who you can hand the patches over to, to do the merge work. Andrew