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=-9.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE, SPF_PASS autolearn=unavailable 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 95B89C433DF for ; Fri, 21 Aug 2020 16:42:05 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 664BD2072D for ; Fri, 21 Aug 2020 16:42:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="LQos0Bys"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="CeUhHNdB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 664BD2072D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:MIME-Version:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Message-Id:Subject:References:In-Reply-To:To:From: Date:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=+Ml9JO90BLE99oaHrSTkeh6/NlLzZVKxMOabqjLRouc=; b=LQos0BysRgSzqvkbgEQbL2M+CK W7Jrlt6Jsg84XrYzJU2e6E+FV7st3a5yS9nwtdDLEUEwJ7hV4GqUja+H8X15KCTv4lQocOhWGhxvJ 8gSe8colPMhTXf9Fu0guPUb9/ECCZTUueBcfOMRN5CO0zr1oNVjXYU/ZwxPmXUTptOZC75SkoDOBP R00P1kP+w+1rrLNvGpkRtDEO+luuAeZwzoyrnb8r2nPEACPhFsg+ClEqdJqUActZWFSbc1JoSM2G0 lPfxaJQigsev42uy6+MnJ2s7q8k5j3rtU727Qi4/q2omyHrCbslGg4naqTdO0cGzK7x8P7MdTkgHF mOL4rBQw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k9A5y-0002Vk-OU; Fri, 21 Aug 2020 16:40:50 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k9A5v-0002Uh-Dw for linux-arm-kernel@lists.infradead.org; Fri, 21 Aug 2020 16:40:48 +0000 Received: from localhost (fw-tnat.cambridge.arm.com [217.140.96.140]) (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 3BC872076E; Fri, 21 Aug 2020 16:40:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1598028046; bh=EvjYX8VGFAkdYRMoROfW5zmgZVwotJ8Uvmvse9ytBIQ=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=CeUhHNdBc9hId5eHJUHIDLQrdIWsAKSe02c8cGLV+g1ypbuJjt0Y8Ef7aZ8jnEFtj Wph7/zFTp9CimZU/MqWma8jD//zRYkCxXgVrZMvXTeOQO0Ks6Rukt6sAZ4EjO1RpFh TrfJrle1LosE+gzUk+697ian3F4pCfZsxwZGbrQg= Date: Fri, 21 Aug 2020 17:40:13 +0100 From: Mark Brown To: Jisheng Zhang , Icenowy Zheng , Bjorn Andersson , Liam Girdwood , Maxime Coquelin , Andy Gross , Support Opensource , Alexandre Torgue In-Reply-To: <20200821111135.0b958d3a@xhacker.debian> References: <20200821111135.0b958d3a@xhacker.debian> Subject: Re: [PATCH v2 00/15] regulator: Fix W=1 build warning when CONFIG_OF=n Message-Id: <159802800846.25815.3400807374016781922.b4-ty@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200821_124047_591596_C47224DA X-CRM114-Status: GOOD ( 14.04 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-stm32@st-md-mailman.stormreply.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 21 Aug 2020 11:11:35 +0800, Jisheng Zhang wrote: > Fixing W=1 build warning when no support for device tree is there. > > Since v1: > - fix the warning with __maybe_unused instead of CONFIG_OF macro > - add 3 more patches to fix the same issue > > Jisheng Zhang (15): > regulator: 88pg86x: Fix W=1 build warning when CONFIG_OF=n > regulator: da9210: Fix W=1 build warning when CONFIG_OF=n > regulator: fan53555: Fix W=1 build warning when CONFIG_OF=n > regulator: fixed: Fix W=1 build warnings when CONFIG_OF=n > regulator: ltc3589: Fix W=1 build warning when CONFIG_OF=n > regulator: ltc3676: Fix W=1 build warning when CONFIG_OF=n > regulator: max1586: Fix W=1 build warning when CONFIG_OF=n > regulator: max77826: Fix W=1 build warning when CONFIG_OF=n > regulator: pwm: Fix W=1 build warning when CONFIG_OF=n > regulator: stm32-pwr: Fix W=1 build warning when CONFIG_OF=n > regulator: stm32-vrefbuf: Fix W=1 build warning when CONFIG_OF=n > regulator: sy8106a: Fix W=1 build warning when CONFIG_OF=n > regulator: qcom-rpmh: Fix W=1 build warning when CONFIG_OF=n > regulator: stm32-booster: Fix W=1 build warning when CONFIG_OF=n > regulator: tps65023: Fix W=1 build warning when CONFIG_OF=n > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [01/15] regulator: 88pg86x: Fix W=1 build warning when CONFIG_OF=n commit: e11e068ccbdb038e21e24ad2ee0157c902e3c9fc [02/15] regulator: da9210: Fix W=1 build warning when CONFIG_OF=n commit: 2d2a84ae30a3bda57a22b283c55be8e9e6fd158b [03/15] regulator: fan53555: Fix W=1 build warning when CONFIG_OF=n commit: 5e97d7e809a1fd8a2401429df13e0410b77d2142 [04/15] regulator: fixed: Fix W=1 build warnings when CONFIG_OF=n commit: 0f037255008386f4ac15a201678e8e4565cd91a3 [05/15] regulator: ltc3589: Fix W=1 build warning when CONFIG_OF=n commit: 8ece31564f1964d52eb1180ee33314c63533947e [06/15] regulator: ltc3676: Fix W=1 build warning when CONFIG_OF=n commit: 1d4c1e02b96ea579f68412980ee1fe5f2ce57d8c [07/15] regulator: max1586: Fix W=1 build warning when CONFIG_OF=n commit: 44bc5d168dc209bddafb3269f72a74c3cbb0d820 [08/15] regulator: max77826: Fix W=1 build warning when CONFIG_OF=n commit: 7bf0a29c354fc1855dc478916211b5194bab4393 [09/15] regulator: pwm: Fix W=1 build warning when CONFIG_OF=n commit: dc8c5ea3574e08e3c7105bbba5af5bb9c055903b [10/15] regulator: stm32-pwr: Fix W=1 build warning when CONFIG_OF=n commit: a94a11ce0d5235e53bb74d54bbd5399c23abfd87 [11/15] regulator: stm32-vrefbuf: Fix W=1 build warning when CONFIG_OF=n commit: d5579e7a2c6aa49a183440eb4e199f4a71543762 [12/15] regulator: sy8106a: Fix W=1 build warning when CONFIG_OF=n commit: bbe26107204eb64e7be1b3433e8b2252edc0b375 [13/15] regulator: qcom-rpmh: Fix W=1 build warning when CONFIG_OF=n commit: a2508eeb8dbdf621518f8c3538d3adcb6960619c [14/15] regulator: stm32-booster: Fix W=1 build warning when CONFIG_OF=n commit: b461ac1cc6c0a0bc4a788d5d65cfd82e5f3bd856 [15/15] regulator: tps65023: Fix W=1 build warning when CONFIG_OF=n commit: 8536bf811dd7a25d90d9128f9db98b5ed8e5bd5c All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel