From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5FCFCC04A6B for ; Wed, 8 May 2019 23:24:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2CACB214AF for ; Wed, 8 May 2019 23:24:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="ANLpXTXc" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728679AbfEHXYA (ORCPT ); Wed, 8 May 2019 19:24:00 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:57318 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726830AbfEHXX7 (ORCPT ); Wed, 8 May 2019 19:23:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=r0DfwmpGBXR6BV7Pz6TDO+BpLqpIYvGRUplJqu3ybfM=; b=ANLpXTXcgQa5gHHGP4sr0ZKWk lBDf7w4WGKrj8YJx18MEzafBVS8yLbU/84cVu+XCIiSHwYuC7kmvPQIz86k5KR7NiEiR1XtdUrgZW JAMpI9P381NuxkS5tALIoItFpzxYvwlGvnPYl35UyyREXnGo0IirnogfCzoOXg62ynsfkgSdGO9Zi xivIw6ZR+HaccUdvpXgthwODFgOBrYt16zSIR3Blg89AcPCM/ywHFZn2g9kUW0QDX3tYbkirHg36H erw3wjHmtXWw1zAkJsAOfsgpN8qBDOT613VPrkByMJIvUyJFx0+xLy+ak0q5J1821lzUX2Zl/JMFJ BpaoV5Z8Q==; Received: from dvhart by bombadil.infradead.org with local (Exim 4.90_1 #2 (Red Hat Linux)) id 1hOVun-0006Rl-Vr; Wed, 08 May 2019 23:23:57 +0000 Date: Wed, 8 May 2019 16:23:56 -0700 From: Darren Hart To: Hans de Goede Cc: Andy Shevchenko , Stephen Boyd , Andy Shevchenko , Kai Heng Feng , Platform Driver , Linux Kernel Mailing List , Semyon Verchenko Subject: Re: [PATCH] platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI table Message-ID: <20190508232356.GA33357@wrath> References: <20190429150135.15070-1-hdegoede@redhat.com> <085c5b6e-d220-ebd1-38d2-def7efca24b8@redhat.com> <568ba27d-a6a5-b158-bab1-f22cd8ccb34e@redhat.com> <155726027056.14659.1724431433952718602@swboyd.mtv.corp.google.com> <10c8864c-6ee7-4dfd-6274-b1996e767653@redhat.com> <20190508225522.GA32286@wrath> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190508225522.GA32286@wrath> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 08, 2019 at 03:55:22PM -0700, Darren Hart wrote: > On Wed, May 08, 2019 at 11:20:52AM +0200, Hans de Goede wrote: > > Hi, > > > > On 08-05-19 10:42, Andy Shevchenko wrote: > > > On Wed, May 8, 2019 at 10:48 AM Hans de Goede wrote: > > > > On 07-05-19 22:17, Stephen Boyd wrote: > > > > > Quoting Hans de Goede (2019-05-06 08:05:42) > > > > > > > > I guess this is urgent? > > > > > > > > Somewhat, getting this into e.g. rc2 would be fine too, waiting till 5.3 > > > > would be bad. > > > > > > So, I can do it as a fixes for rc2, just ping me after merge window. > > > > Ok, will do. > > Andy, what is the issue here? If the dependency is in v5.1 we can do a "merge > --ff-only v5.1" in our for-next branch in order to pull it in, that would be the > same as an immutable branch basically. > A simpler solution for this case would be to issue two PRs to Linus from two different branches. Other subsystems send topic branches, so this isn't out of the ordinary. I have merged the two patches in question from Hans and Steffen to for-next-2. We could send two PRs back to back, with a note to Linus why this is a bit different than usual, and then come back together in our for-next and fixes branches once both are merged and continue as usual. Any concerns with this approach? -- Darren Hart VMware Open Source Technology Center