Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp7690813rdb; Thu, 4 Jan 2024 04:59:04 -0800 (PST) X-Google-Smtp-Source: AGHT+IE6nswSLJo/OaudbFrbRiZgRvBlzz07sjOLsxFzR5nqzWviNrcVBsry68B2WCTsr+J5fW68 X-Received: by 2002:ad4:4ea5:0:b0:67f:ae16:9221 with SMTP id ed5-20020ad44ea5000000b0067fae169221mr560031qvb.108.1704373144268; Thu, 04 Jan 2024 04:59:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704373144; cv=none; d=google.com; s=arc-20160816; b=Nez7EYu4Oh+QcPv+fDmCCN4hSjqk26geNUx7V9CYEzCew7F6mLuuVczZretfvdRcMs gLox9H7IAOHb9p2e810xQfbVu1oLAAsZLx3Wt/UtOfSPNkwvBjZwaTuAcCzz5nN+uwpq /6MKvYM450XO4qjhmYnQ0E5DP0U4sLOvspdotXZqEP4OATo1vmqUhmIi+ygZ72WD0IvJ qxQCHcOCDU+IaiMs/dEkS5q0rj8sGgVl/p+np3Mo0UA7oiPSTm6J113U/Lgmj5fHAm50 oLQuF9yWJLP0YzUQB0b69VPR66Oq+OO/tVwZJ0YzZBSzRaydi6xRZ4z2ak/UjPj1pqDy g5jA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=0jorZOpEoTiklaEKFKiEg4vhBBRoRHs3FD7+t1WT61A=; fh=SeFj8KORm3rQhu2wNVCGDe+b5ksIN3SOLlf/4vuh6aY=; b=Lm07c5GwMNEVemYDPYkYP9a4+CeU5db8i6x4hIxfACI9QaybreU6GSS6weV+23Q3XZ 5Ppp2QSKK2qZmqJ1z9vv1+5NNUZMpTyxqLxSibzlrsvs+T0XVgRBthg10JUf3uVzUs7S xKr8DxwhtgIn9QLAfImxS8ElOJUyzWX84a9+OGxRtMfvLWldWGtJ73Sdbzv4NnOS4+M/ igb4y5wuZl/mJOTmKz63/aclEl2FvwNhKR/zBT+7oiRa/QI6G+/wLjatt7DwnbMLUiSI MuaK8YXvJw9HCVgdZH+I120F7gPfsv1hSZI7aQQrc4AKPYPSdRQJ60FSzaIvVnJkgJA5 cEeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mess.org header.s=2020 header.b=SZrSYppm; spf=pass (google.com: domain of linux-kernel+bounces-16667-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-16667-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mess.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id r19-20020a0ccc13000000b0067f8a6faa71si21105554qvk.224.2024.01.04.04.59.04 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Jan 2024 04:59:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-16667-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=pass header.i=@mess.org header.s=2020 header.b=SZrSYppm; spf=pass (google.com: domain of linux-kernel+bounces-16667-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-16667-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mess.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id E77551C21E60 for ; Thu, 4 Jan 2024 12:59:03 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 0D9C922339; Thu, 4 Jan 2024 12:58:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mess.org header.i=@mess.org header.b="SZrSYppm" X-Original-To: linux-kernel@vger.kernel.org Received: from gofer.mess.org (gofer.mess.org [88.97.38.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3B7DC22324; Thu, 4 Jan 2024 12:58:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=mess.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mess.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mess.org; s=2020; t=1704372628; bh=2rIYho0tJC4fQVeP6/cBbLHX5whOI1hHP2hPbbpgze8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=SZrSYppmG8kRGCUnosr7aniaaMeadcFKNVy6SrMe0d79B4F/ByDaAeDIGTX/P8e7I PJgo+r+eT2+uz3IsN65cwhk75HOmuguHYscVpN9fsAwoxjxS+WSto/KiQsIcRQHAfZ 6lX1MZG2Z5lNSpxrW28GC3VClCxPkEVO9z9FDqO/5StIj7zdcUjTMxAsvfQBJKq81q ufyR0eMIKfjOXLtEWz6cLRQ8xdU2Zk+R7Ebg1Okla5Iy/gDbSxmYEQQlHb2k+MH6bp xhOV1HF11uummEJ1SAyhW1W5aDsEK84tKOqMwC7Pg2qw+Dmi5g4BfvF4eP2a7lryxg G5v0Fqb9AInFg== Received: by gofer.mess.org (Postfix, from userid 1000) id 1760F1000FC; Thu, 4 Jan 2024 12:50:28 +0000 (GMT) Date: Thu, 4 Jan 2024 12:50:28 +0000 From: Sean Young To: Bagas Sanjaya Cc: Thierry Reding , Lee Jones , Jingoo Han , Linus Torvalds , Stephen Rothwell , Flavio Suligoi , Linux Kernel Mailing List , Linux Next Mailing List , Linux DRI Development Subject: Re: (subset) linux-next: build failure after merge of the pwm tree Message-ID: References: <20231221165805.0c4771c1@canb.auug.org.au> <170316329164.542553.8341559295114557258.b4-ty@kernel.org> <20231221125801.GG10102@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Thu, Jan 04, 2024 at 05:02:41PM +0700, Bagas Sanjaya wrote: > [also add Jingoo (additional backlight maintainer) and Linus] > > On Thu, Dec 21, 2023 at 07:34:57PM +0100, Thierry Reding wrote: > > On Thu, Dec 21, 2023 at 12:58:01PM +0000, Lee Jones wrote: > > > On Thu, 21 Dec 2023, Lee Jones wrote: > > > > > > > On Thu, 21 Dec 2023 16:58:05 +1100, Stephen Rothwell wrote: > > > > > After merging the backlight tree, today's linux-next build (x86_64 > > > > > allmodconfig) failed like this: > > > > > > > > > > drivers/video/backlight/mp3309c.c: In function 'mp3309c_bl_update_status': > > > > > drivers/video/backlight/mp3309c.c:134:23: error: implicit declaration of function 'pwm_apply_state'; did you mean 'pwm_apply_args'? [-Werror=implicit-function-declaration] > > > > > 134 | ret = pwm_apply_state(chip->pwmd, &pwmstate); > > > > > | ^~~~~~~~~~~~~~~ > > > > > | pwm_apply_args > > > > > > > > > > [...] > > > > > > > > Applied, thanks! > > > > > > > > [1/1] linux-next: build failure after merge of the pwm tree > > > > commit: f7baa9ccef93ba1c36a8ecf58c2f4e86fb3181b9 > > > > > > Actually it's: > > > > > > f7baa9ccef93b ("backlight: mp3309c: Rename pwm_apply_state() to pwm_apply_might_sleep()") > > > > > > But don't bank on the commit ID staying the same. > > > > This is likely going to break the build on your branch because > > pwm_apply_might_sleep() is only available in the PWM tree right now. In > > any case, I've now pushed a commit that adds pwm_apply_state() back as a > > compatibility stub, so it should be okay for you to drop this if you > > run into problems. It's always possible that somebody else wants to add > > a new caller of pwm_apply_state() and in retrospect we should've > > probably done this from the start, at least as a transitional measure > > for one or two cycles. > > > > Hi Lee and Thierry, > > I know that we're still on New Year vibes, so some things are not up to full > steam for now; but since we're close to v6.7 release and v6.8 merge window, > hence allow me to ask: > > Stephen Rothwell is still complaining about backlight tree build failure > due to f7baa9ccef93b, yet it has not been fixed so far. Has the culprit > been dropped/reverted as he requested? The worst case is the culprit slips > through and become part of backlight PR and Linus will likely not happy > with the build regression (maybe he had to fix by himself). This should be fixed by 9a216587a03df, and on current linux-next I can't reproduce the problem any more (x86_64 allmodconfig). Thanks, Sean