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 62E12EB64DD for ; Thu, 20 Jul 2023 15:22:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232089AbjGTPWJ (ORCPT ); Thu, 20 Jul 2023 11:22:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57738 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230220AbjGTPWH (ORCPT ); Thu, 20 Jul 2023 11:22:07 -0400 Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C69371B9 for ; Thu, 20 Jul 2023 08:22:05 -0700 (PDT) Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-682eef7d752so201056b3a.0 for ; Thu, 20 Jul 2023 08:22:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mihalicyn.com; s=mihalicyn; t=1689866525; x=1690471325; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5jNhnR+ye5SEakvh+tGW6i8mQKb+NDXkkhU62vn/+c8=; b=eh5OTxF8ssTPMy9eN4Nln0Kvg4S0wZoft2ke4YL3WqLJstWote7jOp6Dk/6M2Y7SeT h3qS0ic62YlflNjqq/LynK9RdNAm/+ZFQE+zQgIB1HvRmIFLmjoawgRnl1wcEqKSGMWL q10NL06sl+Bq7jAvh3LzDmky1K+DzgYHyu91Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689866525; x=1690471325; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5jNhnR+ye5SEakvh+tGW6i8mQKb+NDXkkhU62vn/+c8=; b=E2IyiO8tUpSG6Y02zOT7lSkvKYJzJASL0b9gEqvM+GUdrCRG9UiOx6t/uoCr4Nw7eq VTR+9riQTTJ5+P1qa8MxpQzgob7e+BDSIZqDbSVaCAQdjEIHBMRlp1vocEp6BSRiGy/H KGDE8rVR+S8vo3SV0PiP/H21+0jJcs4xJP8pOrFp7FrujBjCMwY8ngqt8QGQ21BdmQ67 tQZeEy4qtZX4LLx+UPGSkq3KvvqI+2g5zFidvGyniKUkfZj7V39bQY5EIN75Fh55VNrE z4llA5gcbnbmmzYT51kCAQRXGeBxohEH1V6qSWyvSnIBZPS2D7w2bwk+eBIT+XEL+ruR gV0w== X-Gm-Message-State: ABy/qLZE1ge/B3nosL4FU6RQzgy8v27/XKlpBq+f0diPDoOHCNCX9DAP cNchIv2miTKROEtLJZnf2tohOGK781aVsFM/5aJZ7M1pwFUYX/zHyktSjQkv X-Google-Smtp-Source: APBJJlE4X/A4ZMOioySFAnqd/G3ycv8NyoRPzE5yjcSpeiSNUnhUyl95syR+9ELPrn/tFVkseHIGaEyFiVMv0WVPSJY= X-Received: by 2002:a05:6a00:988:b0:686:2526:ee7d with SMTP id u8-20020a056a00098800b006862526ee7dmr3493442pfg.0.1689866525264; Thu, 20 Jul 2023 08:22:05 -0700 (PDT) MIME-Version: 1.0 References: <20230720105042.64ea23f9@canb.auug.org.au> <20230719182439.7af84ccd@kernel.org> <20230720130003.6137c50f@canb.auug.org.au> <20230719202435.636dcc3a@kernel.org> <20230720081430.1874b868@kernel.org> In-Reply-To: <20230720081430.1874b868@kernel.org> From: Alexander Mikhalitsyn Date: Thu, 20 Jul 2023 17:21:54 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the bluetooth tree To: Jakub Kicinski Cc: "Von Dentz, Luiz" , Stephen Rothwell , Marcel Holtmann , Johan Hedberg , Linux Kernel Mailing List , Linux Next Mailing List , David Miller , Paolo Abeni , Networking , Kuniyuki Iwashima Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 20, 2023 at 5:14=E2=80=AFPM Jakub Kicinski wr= ote: > > On Wed, 19 Jul 2023 20:24:35 -0700 Jakub Kicinski wrote: > > On Thu, 20 Jul 2023 03:17:37 +0000 Von Dentz, Luiz wrote: > > > Sorry for not replying inline, outlook on android, we use scm_recv > > > not scm_recv_unix, so Id assume that change would return the initial > > > behavior, if it did not then it is not fixing anything. > > > > Ack, that's what it seems like to me as well. > > > > I fired up an allmodconfig build of linux-next. I should be able > > to get to the bottom of this in ~20min :) > > I kicked it off and forgot about it. > allmodconfig on 352ce39a8bbaec04 (next-20230719) builds just fine :S Dear Jakub, Thanks for checking! As I can see linux-next tree contains both patches: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?h= =3Dnext-20230719&qt=3Dgrep&q=3DForward+credentials+to+monitor So, the fix is working, right? Kind regards, Alex