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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CF1FBC433EF for ; Fri, 22 Oct 2021 10:31:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B210C611F2 for ; Fri, 22 Oct 2021 10:31:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232690AbhJVKdu (ORCPT ); Fri, 22 Oct 2021 06:33:50 -0400 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:55807 "EHLO wout3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232573AbhJVKds (ORCPT ); Fri, 22 Oct 2021 06:33:48 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id DD65B3200A1E; Fri, 22 Oct 2021 06:31:30 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute3.internal (MEProxy); Fri, 22 Oct 2021 06:31:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alistair23.me; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm2; bh=KbMpnRh1mWwjoX89UJ/WIrnsgzEo huauhd3dYa3aqWQ=; b=R9bFt/6UFPwHQr8DQO6aCJbcQIJIwqBGhBfPKUV2GpLB 99WYb/K7rOvMFJv6E0HbSgdpOtnun6Zdg+hcE+NcopHSfTV1kv8R6JYPgnN1GyAo plGZsqHhGt0KxCsftm7e5sDZa6dCTVi2UbbQG9p5JXP444JGKlQ8kMtYOZ3smpLZ +r9gxTmMQLUyHv0O4cr65i/qblEiy5xZXhr3Fyiw6WptwQj+hRwE7c2K1JVln2mb TX9dd5DQmhFgCDf37/98IKO6Swqile9nr4R4ZwboQsAiHnkeulh42UMKUDEH26jj NmfdPuVtv1iIlZO6G74mS/BOalK4lIIsn1nysgmu1w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=KbMpnR h1mWwjoX89UJ/WIrnsgzEohuauhd3dYa3aqWQ=; b=babQCnMTJIsdx1498obkxE 1e/jsWUbFsLUKg4LvJuf4RqvqJjm9BjWIZ3fhFpGoeFnUZ/aEV5R6nv7xVFfQn4S 3kCeonT3UHodPFskBqYxHoYbV9Uxas1z1O2tbMK+mmNmo8kv1hadlOiSmXUHhP3V 1t8aTzy1BW0n+eadmtQ59dO9rbuFW8n2Di7Uq/75bbH23uDs9crMuxB37kuFreEm DutXlpA8+eVMSnDxFM5CmW8uFO4FzZtT4JDy0sUwirq69E5McQajw4CBf1QhoWDe 0lLUPDYzLcMQWmAUAp+7IBCMf2rSSWxmzZmCXww6ODNzPvgAqIwz/Vl/lE8wnhIw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddvkedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomheptehlihhs thgrihhruceorghlihhsthgrihhrsegrlhhishhtrghirhdvfedrmhgvqeenucggtffrrg htthgvrhhnpeeuffekveehjeeltdeuveeikeelkeejhfejheduhfdtgfdtgfejjeekvdev jeevueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grlhhishhtrghirhesrghlihhsthgrihhrvdefrdhmvg X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id DAD0AAC0DD1; Fri, 22 Oct 2021 06:31:29 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-1369-gd055fb5e7c-fm-20211018.002-gd055fb5e Mime-Version: 1.0 Message-Id: In-Reply-To: <20211022125323.132b950d@canb.auug.org.au> References: <20211022125323.132b950d@canb.auug.org.au> Date: Fri, 22 Oct 2021 20:31:08 +1000 From: Alistair To: "Stephen Rothwell" , "Mark Brown" , "Liam Girdwood" Cc: "Linux Kernel Mailing List" , "Linux Next Mailing List" Subject: Re: linux-next: build failure after merge of the regulator tree Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 22, 2021, at 11:53 AM, Stephen Rothwell wrote: > Hi all, > > After merging the regulator tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/regulator/sy7636a-regulator.c:14:10: fatal error: linux/mfd/sy7636a.h: No such file or directory > 14 | #include > | ^~~~~~~~~~~~~~~~~~~~~ > > Caused by commit > > cb17820ef71e ("regulator: sy7636a: Remove requirement on sy7636a mfd") The above patch allows the sy7636a regulator to be built, as it no longer depends on the mfd driver directly. This fails to build on current upstream as the sy7636a header file isn't upstream yet. The header file is added earlier in the patch series. This patch should probably not be applied until after: mfd: simple-mfd-i2c: Enable support for the silergy,sy7636a Or if preferred I can split adding the header file into it's own patch that can be applied. Alistair > > I have used the regulator tree from next-20211021 for today. > > -- > Cheers, > Stephen Rothwell >