Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4168534yba; Tue, 7 May 2019 13:19:04 -0700 (PDT) X-Google-Smtp-Source: APXvYqwp6WljuHE/k3T9Il1/VsUPZZmISyrzleZbb8OuiqG3hlSGQjhaLERJNlC7M9eM/oSH+DA0 X-Received: by 2002:a63:5c4c:: with SMTP id n12mr42266066pgm.111.1557260344198; Tue, 07 May 2019 13:19:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557260344; cv=none; d=google.com; s=arc-20160816; b=gZMXTkfB72OMnf+gSjAXaIn1Z9fC5dd9pVqpb39aUVjoIDVKBt4nIjmV4D85yKzTfo faBFJJ0rmkBOplAz3HgWIb5pEUN359x/qXt4+tDJKwS2Fy9Cy7uGZEChaJGNbzZcN3lS P2rnBta4HgLTZvTUmgt9YtaEOPqoV4LEmy1TVwm0DWbR1yEjFzX93XSfdJTovNNIDISg jPmnOAkdpNYTrF1hlggzXZx7efRzIa4bYTmAnN/fWjwAYKxk/rZzS5fhPE17PsoF6YCL 45Heh1cHIK9QnKSa++e5h1qkPWtxJ1ujjAqpaXHEf68zRNv9BIqE04yEHbizsYDWDbmk +ABg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:user-agent:message-id:to:cc:subject :from:references:in-reply-to:content-transfer-encoding:mime-version :dkim-signature; bh=Zp/rnTfJkpJZNmoGs+xBSvXnImnrSx0zg7++B1WSdz8=; b=zNIaYHLfNmDmH3Bxr5PD31nsInFsfQiXUKXRLceLhR12QyTkSugHTHSSiP6WodlXer VWUnOyBxbN0K0N/j03FMD1OamjrVJWFQZkbqKKuD17m1kwU92a1v+gc+YzPLIIgz7iWj EEjbjr/YXxhO/nhbLpfPFd418itBVd3tyjzVNYcsOJvHN7xLhUMwswnAfEDz8VhEl7jp eo6OEW1c0GIW49gpj6z+Ijh61ypjBba0CwUw6hwujAuP2eLQ9tzyf8+4WtmRibuVx3ku lFUhzdJMvfbOO8g0ErLa8BUQLrBy5hJWi06Wh/knQVNFhZmc0iRLOkQTTx6JYzd0tWUB XBHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wpdR9llH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y22si19769994pfe.141.2019.05.07.13.18.47; Tue, 07 May 2019 13:19:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wpdR9llH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726679AbfEGURw (ORCPT + 99 others); Tue, 7 May 2019 16:17:52 -0400 Received: from mail.kernel.org ([198.145.29.99]:60538 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726225AbfEGURw (ORCPT ); Tue, 7 May 2019 16:17:52 -0400 Received: from localhost (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8D9EC20675; Tue, 7 May 2019 20:17:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557260271; bh=Zp/rnTfJkpJZNmoGs+xBSvXnImnrSx0zg7++B1WSdz8=; h=In-Reply-To:References:From:Subject:Cc:To:Date:From; b=wpdR9llHaGX6478IU1bK4g5PgQ41VfPDmGa02s8bbErr25gTi/YY3ft5eWwqdZ6sv t+PVm5NU/PTcy6AEvXpIP9ADhatNWb2Fbd+geG2mTQlXY6i5VBtXyTgL8KZ7skYkpE tdoIrsWbWRGrNjq4uPobzwYdg0Dr8cuk1MCwHXDI= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <568ba27d-a6a5-b158-bab1-f22cd8ccb34e@redhat.com> References: <20190429150135.15070-1-hdegoede@redhat.com> <085c5b6e-d220-ebd1-38d2-def7efca24b8@redhat.com> <568ba27d-a6a5-b158-bab1-f22cd8ccb34e@redhat.com> From: Stephen Boyd Subject: Re: [PATCH] platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI table Cc: Darren Hart , Andy Shevchenko , Kai Heng Feng , Platform Driver , Linux Kernel Mailing List , Semyon Verchenko To: Andy Shevchenko , Hans de Goede Message-ID: <155726027056.14659.1724431433952718602@swboyd.mtv.corp.google.com> User-Agent: alot/0.8 Date: Tue, 07 May 2019 13:17:50 -0700 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Hans de Goede (2019-05-06 08:05:42) > Hi, >=20 > On 06-05-19 16:59, Andy Shevchenko wrote: > > On Mon, May 6, 2019 at 5:47 PM Hans de Goede wrot= e: > >> > >> Hi, > >> > >> On 06-05-19 14:38, Andy Shevchenko wrote: > >>> On Mon, Apr 29, 2019 at 6:01 PM Hans de Goede w= rote: > >>>> > >>>> The Lex 3I380D industrial PC has 4 ethernet controllers on board > >>>> which need pmc_plt_clk0 - 3 to function, add it to the critclk_syste= ms > >>>> DMI table, so that drivers/clk/x86/clk-pmc-atom.c will mark the cloc= ks > >>>> as CLK_CRITICAL and they will not get turned off. > >>>> > >>> > >>> Acked-by: Andy Shevchenko > >>> supposedly to go via CLK tree. > >>> > >>> P.S. If you want it through PDx86, I need immutable branch / tag from= CLK. > >> > >> Stephen added the patches this depends on to his fixes branch, so they > >> are in the 5.1 / Torvald's master branch, since we are now in the 5.2 = merge > >> window, you should be able to cleanly apply this directly. > >=20 > > We don't do back merges, so, our base is v5.1-rc1. Does it mean the > > commit in question is in v5.1-rc1? > > AFAICS it was appeared in v5.1-rc5. >=20 > Ah, I see, my bad. >=20 > Stephen can you pick up this patch and the > "[PATCH 1/1] Add several Beckhoff Automation boards to critclk_systems DM= I table" > patch then? >=20 I guess this is urgent? I'm lost why Andy can't apply the patch and merge it up to Linus. I don't maintain this driver here, and even if there's a cross tree dependency I don't understand why a base of v5.1-rc1 is limiting abilities to apply patches. I'd think that if an "immutable branch" was all that was required you could 'git checkout 7c2e07130090ae001a97a6b65597830d6815e93e' and then apply the patch there and merge it all up into the PDx86 tree. In the end, when sending the PR to Linus the already merged changes won't show up in the diff because it's all been merged already on the other side. Either way, I'm going to send off the clk PR real soon so this may need to wait until after the merge window, or if it's really urgent I could send a fixes branch before the merge window closes next week.