From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752862AbbIONeH (ORCPT ); Tue, 15 Sep 2015 09:34:07 -0400 Received: from arrakis.dune.hu ([78.24.191.176]:57849 "EHLO arrakis.dune.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751855AbbIONeA (ORCPT ); Tue, 15 Sep 2015 09:34:00 -0400 Subject: Re: spi/bcm63xx: unknown CONFIG_BIG_ENDIAN To: Mark Brown References: <20150915062400.GA9130@i4lab-dhcp156.informatik.uni-erlangen.de> <55F7CB6E.1090008@openwrt.org> <20150915084012.GB11268@sirena.org.uk> Cc: Valentin Rothberg , Paul Bolle , ziegler@cs.fau.de, linux-kernel@vger.kernel.org From: Jonas Gorski Message-ID: <55F81E59.70703@openwrt.org> Date: Tue, 15 Sep 2015 15:34:17 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150915084012.GB11268@sirena.org.uk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15.09.2015 10:40, Mark Brown wrote: > On Tue, Sep 15, 2015 at 09:40:30AM +0200, Jonas Gorski wrote: > >> Mark? If you can drop patches 2 to 4 that would be easiest for me, but if >> you don't do rebases on your for-next branch, then I'll rewrite the >> patches to apply on top of the already applied old versions and send a v3. > > No, please submit incremental modifications as incremental > modifications. IS there anything I can do to avoid this happining again, like a patchwork where I can mark my older versions as superseded? I admit I didn't expect partial application of the (old) series. Jonas