From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753169AbaKDMri (ORCPT ); Tue, 4 Nov 2014 07:47:38 -0500 Received: from smtp102.mer-nm.internl.net ([217.149.192.138]:36072 "EHLO smtp102.mer-nm.internl.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866AbaKDMrg convert rfc822-to-8bit (ORCPT ); Tue, 4 Nov 2014 07:47:36 -0500 X-Spam-Flag: NO X-Spam-Score: -2.899 X-Spam-Languages: en Message-ID: <5458CAE4.4080809@topic.nl> Date: Tue, 4 Nov 2014 13:47:32 +0100 From: Mike Looijmans User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Mark Brown CC: , Subject: Re: [PATCH v2] Add ltc3562 voltage regulator driver References: <1414570560-10320-2-git-send-email-mike.looijmans@topic.nl> <1414668415-597-1-git-send-email-mike.looijmans@topic.nl> <20141030165133.GB18557@sirena.org.uk> <54573860.4060708@topic.nl> <20141103120919.GE3815@sirena.org.uk> <545795D8.1040600@topic.nl> <20141103151058.GP3815@sirena.org.uk> <5457BD85.2070901@topic.nl> <54589472.8030305@topic.nl> <20141104113417.GG3815@sirena.org.uk> In-Reply-To: <20141104113417.GG3815@sirena.org.uk> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8BIT X-Originating-IP: [192.168.80.45] X-EXCLAIMER-MD-CONFIG: 9833cda7-5b21-4d34-9a38-8d025ddc3664 X-EXCLAIMER-MD-BIFURCATION-INSTANCE: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/04/2014 12:34 PM, Mark Brown wrote: > On Tue, Nov 04, 2014 at 09:55:14AM +0100, Mike Looijmans wrote: >> On 11/03/2014 06:38 PM, Mike Looijmans wrote: > >>>> You need to develop against current versions of the kernel, this is >>>> something that was merged into Linus' tree during the merge window. > >>> Is this an absolute show-stopper for you? > >>> With some effort I could move from our current 3.15 to 3.17, but even that >>> wouldn't be recent enough then. I can justify spending a few days on getting >>> the driver integrated into mainline, even if the initial version cost less >>> than that; but moving everything to mainline is going to take weeks and the >>> boss is definitely going to say "no" to that. > > It should be easy to backport the support into your current kernel, it's > just a few commits and there hasn't been much development in this area > of the code. Can you take a look at doing that please? That option hadn't crossed my mind yet, I'll look into it. > >> More important than that: Since this chip powers the IO banks, we need it >> for our own products, and hence it has to work (also) on the current 3.15 >> kernel. Using APIs from 3.18 wouold render the driver useless to ourselves. > > This is just not at all important upstream, sorry. The kernel moves on > and internal APIs within the kernel move on so it is expected that code > used in production won't be the latest and greatest upstream code. I realize that, but then the result would be that I'll stop working on getting the driver into mainline and force customers to use a patch or use our fork of linux. Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Systems Eindhovenseweg 32-C, NL-5683 KH Best Postbus 440, NL-5680 AK Best Telefoon: (+31) (0) 499 33 69 79 Telefax: (+31) (0) 499 33 69 70 E-mail: mike.looijmans@topic.nl Website: www.topic.nl Please consider the environment before printing this e-mail Topic zoekt gedreven (embedded) software specialisten! http://topic.nl/vacatures/topic-zoekt-software-engineers/