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 4D6E2C7619A for ; Mon, 27 Mar 2023 09:15:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232827AbjC0JP0 (ORCPT ); Mon, 27 Mar 2023 05:15:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232345AbjC0JPY (ORCPT ); Mon, 27 Mar 2023 05:15:24 -0400 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 477AF3C26; Mon, 27 Mar 2023 02:15:23 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E602D5C00FE; Mon, 27 Mar 2023 05:15:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 27 Mar 2023 05:15:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1679908520; x=1679994920; bh=A5 +gI2srvfn+f8eE2nwKRdqo4mc6G9sjufQGQbcwNyg=; b=aXkRMHccd8a4geZ+52 uwp9RwQecgEi3YJNVgKAQ+ZqZyt4Y2dAVO2gdQunyAGOPra/SG5mU0XkziDtZJay VKAK4oMU7QQ27FHnmCpEkLRnsYbCi56S0ORgv3zejaQjAPrP71SGhq0kXH43ovCR l+wHsqbP3+flivnMycP7t56gsJKFc2jMUG+rHdT+K3Nlb0v0gU3lObSvaxFJLO6+ TEDT8REeOTTbVifNqqkIpyQTckwg8r7oXwfN+MxIunr7mncxCRdI+HuWr7Lkm6Kn ahdgbnUgOrFIXc2G5iJ7lKf+10an8VR8AMRxRm7C7sjKYqlrFHzRUzXJBUsZP56V Yojg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1679908520; x=1679994920; bh=A5+gI2srvfn+f 8eE2nwKRdqo4mc6G9sjufQGQbcwNyg=; b=CMiPOPKE7dMI3gBff9OWxR9YwKMrk AVvjTC2iDWQppJUw/3VTompsO19d8EmtSxPwMeJ+vF0bqS6k4/AJJDOL/+kMqL4t r1lsAl+O+0Alp2P8lKU8jZPiIkE7UH/y/gQ06Z+YYInlkdl9d2gd+8M+lDukZTr8 KGF8Az1v197Twkb3PsBiN1E2U7V2xFBtnPgoiSbERcapCdK07ZE0zA8zg3HjUd11 xPnasqVVLo1JX+N8uW9FLJCmSA+hXZp8u1ERm4Znnw7njsMTyi78PqrWo2tzcaTY noThQoYVa0G80lVKvUCVgyMxOlPD9SpD1y6HYSv+B5/MMsiW2Yo2Dq0Jg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdehvddgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepheegvd evvdeljeeugfdtudduhfekledtiefhveejkeejuefhtdeufefhgfehkeetnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorg hhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 27 Mar 2023 05:15:19 -0400 (EDT) Date: Mon, 27 Mar 2023 11:15:16 +0200 From: Greg KH To: Stephen Rothwell Cc: Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Harald Freudenberger , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the driver-core tree Message-ID: References: <20230327154655.58dd627d@canb.auug.org.au> <20230327192215.060fd858@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230327192215.060fd858@canb.auug.org.au> Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Mon, Mar 27, 2023 at 07:22:15PM +1100, Stephen Rothwell wrote: > Hi All, > > On Mon, 27 Mar 2023 09:33:42 +0200 Greg KH wrote: > > > > Patch is correct, thank you. > > Thanks for checking. > > > s390 developers, if you have a persistent tag/branch, I can suck this > > into the driver core tree and apply this fixup there so that you don't > > have to deal with any merge issues for 6.4-rc1 if you want. Or I can > > provide one for you if you need/want that instead. Or we can just leave > > it alone and deal with it during the 6.4-rc1 merge window, your choice. > > Or (it being pretty trivial) you could both just let Linus know when > you send your merge requests ... True, that works for me!