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 4F2BDC4332F for ; Tue, 18 Oct 2022 12:29:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230131AbiJRM3l (ORCPT ); Tue, 18 Oct 2022 08:29:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52804 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230094AbiJRM3h (ORCPT ); Tue, 18 Oct 2022 08:29:37 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 377A3EA7; Tue, 18 Oct 2022 05:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666096172; x=1697632172; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=PaE+ltoOm4ofs4LgjGMXlY2Byk9Xcbkppn+A/cYaqjM=; b=Y9IvJopAe+JXXpohSP6ERAgDC/rins/fwzUjgkXZP0qwvhjJcsZciglX ut1YLKUxr59ogh2IqWDrE3yD7sslxSq6qi2CMs4Y6l7DxxeeXmkPxJ4JI KynLlCDrOneDmecXi1NKZo7HAJb10qtnznk8EQXeHyWESDbG849UKygnx HNXDyFqMxmRCySptB3KnPGU5apacmaRpMRUpvD8CQ5XaVzmThDm7yPorf 34Vs05XDO7BKqg626l5a4BziAFVsCkPDUDNVjIBPho5/xZoxHcqwgis84 WxS6IDPk9JILcvEUdgez/5ztK4epzhiHJelrQLseEGTB63boe/yYUol/J A==; X-IronPort-AV: E=McAfee;i="6500,9779,10503"; a="304826541" X-IronPort-AV: E=Sophos;i="5.95,193,1661842800"; d="scan'208";a="304826541" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Oct 2022 05:29:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10503"; a="659768037" X-IronPort-AV: E=Sophos;i="5.95,193,1661842800"; d="scan'208";a="659768037" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga008.jf.intel.com with ESMTP; 18 Oct 2022 05:29:27 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oklio-009M5d-2g; Tue, 18 Oct 2022 15:29:26 +0300 Date: Tue, 18 Oct 2022 15:29:26 +0300 From: Andy Shevchenko To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the pinctrl-intel tree Message-ID: References: <20221018131330.75fc1807@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221018131330.75fc1807@canb.auug.org.au> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 18, 2022 at 01:13:30PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the pinctrl-intel tree, today's linux-next build (arm64 > defconfig) failed like this: > > > Presumably caused by commit > > e6b665a1c9ae ("pinctrl: Clean up headers") > > I have applied the following patch for today. > > From: Stephen Rothwell > Date: Tue, 18 Oct 2022 13:06:39 +1100 > Subject: [PATCH] fix up for "pinctrl: Clean up headers" > > Signed-off-by: Stephen Rothwell > --- > drivers/pinctrl/pinctrl-zynqmp.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/pinctrl/pinctrl-zynqmp.c b/drivers/pinctrl/pinctrl-zynqmp.c > index 1a94db1ffa4f..f2be341f73e1 100644 > --- a/drivers/pinctrl/pinctrl-zynqmp.c > +++ b/drivers/pinctrl/pinctrl-zynqmp.c > @@ -18,6 +18,7 @@ > #include > > #include > +#include > #include > #include Right, thank you for the fix, I'll incorporate it into the original patch. -- With Best Regards, Andy Shevchenko