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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BC56AC433F5 for ; Sat, 26 Feb 2022 15:08:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230391AbiBZPJO (ORCPT ); Sat, 26 Feb 2022 10:09:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41652 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230315AbiBZPJM (ORCPT ); Sat, 26 Feb 2022 10:09:12 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EA79C1DC9A2; Sat, 26 Feb 2022 07:08:36 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6C0C660B89; Sat, 26 Feb 2022 15:08:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4D360C340E8; Sat, 26 Feb 2022 15:08:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1645888115; bh=ijmknrhdQP18Q3RIGWdlxw9x4DRN8zfnfy7bwDbty/A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=zeAx8OoHqjb05X0iSOHmFdz5gHsJZH2RRa0qOwRW4Afu7B5/3Cx7Ecnc6PIZDb8yg 2BAFCTCdQE55GcHlKltTZLWtqLPoys2qurnm2WgFUO1U/gAj3pXvTwN1RpdVOI+T49 f+th7ooD43Yjwj4xAtkmXqmxRfIYKMcqujyqd6bw= Date: Sat, 26 Feb 2022 16:08:32 +0100 From: Greg KH To: broonie@kernel.org, Kai-Heng Feng Cc: Arnd Bergmann , Ulf Hansson , Linux Kernel Mailing List , Linux Next Mailing List , linux-mmc@vger.kernel.org Subject: Re: linux-next: build failure after merge of the char-misc tree Message-ID: References: <20220225204055.3899986-1-broonie@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220225204055.3899986-1-broonie@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Fri, Feb 25, 2022 at 08:40:55PM +0000, broonie@kernel.org wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86 > allmodconfig) failed like this: > > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sd_request': > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:809:17: error: unused variable 'dev' [-Werror=unused-variable] > 809 | struct device *dev = &host->pdev->dev; > | ^~~ > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_set_ios': > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1084:17: error: unused variable 'dev' [-Werror=unused-variable] > 1084 | struct device *dev = &host->pdev->dev; > | ^~~ > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_get_ro': > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1133:17: error: unused variable 'dev' [-Werror=unused-variable] > 1133 | struct device *dev = &host->pdev->dev; > | ^~~ > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_get_cd': > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1159:17: error: unused variable 'dev' [-Werror=unused-variable] > 1159 | struct device *dev = &host->pdev->dev; > | ^~~ > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_switch_voltage': > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1258:17: error: unused variable 'dev' [-Werror=unused-variable] > 1258 | struct device *dev = &host->pdev->dev; > | ^~~ > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_execute_tuning': > /tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1311:17: error: unused variable 'dev' [-Werror=unused-variable] > 1311 | struct device *dev = &host->pdev->dev; > | ^~~ > cc1: all warnings being treated as errors > > Caused by commit > > 7570fb41e450ba37 ("mmc: rtsx: Let MMC core handle runtime PM") > > I have used the char-misc tree from yesterday instead. Kai-Heng, can you send an add-on patch to fix this? thanks, greg k-h