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 B78AEC4332F for ; Mon, 12 Dec 2022 23:30:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234006AbiLLXaY (ORCPT ); Mon, 12 Dec 2022 18:30:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233744AbiLLXaU (ORCPT ); Mon, 12 Dec 2022 18:30:20 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 33A521ADAB for ; Mon, 12 Dec 2022 15:30:19 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8699961298 for ; Mon, 12 Dec 2022 23:30:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id EA235C433F1; Mon, 12 Dec 2022 23:30:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670887818; bh=iGRSSOoGM0SSodg+Ay5Zit9N2m46ln5I4GA2lAyVA/E=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=sfGlnRoTMV44nlFwsjDGOzw4ELX7UhtXPUP+2V6MwkX2fujEvMiXnaHrI0fr+dSL2 9E8aSy4SGxOC2kAdSXLFuvMcMeVOjIDYMJK2RzPH+gOP5L3BtlhF7ItgQG8uejK3n+ yFHgaMDkSxKhqPlWYNGRJsu5x4FqyfXXjB63m4ueRU7dNb2l8Io70V3hyvePPIKbQ+ zqNWu0WLj9FIajoCL+7NRyrd2bx15ut86G0/MSoVurUjkaQJ6kuK+2Q9vizyqSPzfb OMgvjkEOvqrqjZNzgMmVf2XC1MZE6wZeWqBGJxAOH4E6o0/PGAJ6mGOb5uGimwpQz/ XDOrICV5D7NNA== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id D697BC41606; Mon, 12 Dec 2022 23:30:17 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH net-next 0/3] net: add IFF_NO_ADDRCONF to prevent ipv6 addrconf From: patchwork-bot+netdevbpf@kernel.org Message-Id: <167088781787.32014.12569414144216569163.git-patchwork-notify@kernel.org> Date: Mon, 12 Dec 2022 23:30:17 +0000 References: In-Reply-To: To: Xin Long Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org, edumazet@google.com, pabeni@redhat.com, jiri@resnulli.us, j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net, sridhar.samudrala@intel.com, stephen@networkplumber.org, liali@redhat.com Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello: This series was applied to netdev/net-next.git (master) by Jakub Kicinski : On Fri, 9 Dec 2022 10:21:37 -0500 you wrote: > This patchset adds IFF_NO_ADDRCONF flag for dev->priv_flags > to prevent ipv6 addrconf, as Jiri Pirko's suggestion. > > For Bonding it changes to use this flag instead of IFF_SLAVE > flag in Patch 1, and for Teaming and Net Failover it sets > this flag before calling dev_open() in Patch 2 and 3. > > [...] Here is the summary with links: - [net-next,1/3] net: add IFF_NO_ADDRCONF and use it in bonding to prevent ipv6 addrconf https://git.kernel.org/netdev/net-next/c/8a321cf7becc - [net-next,2/3] net: team: use IFF_NO_ADDRCONF flag to prevent ipv6 addrconf https://git.kernel.org/netdev/net-next/c/0aa64df30b38 - [net-next,3/3] net: failover: use IFF_NO_ADDRCONF flag to prevent ipv6 addrconf https://git.kernel.org/netdev/net-next/c/cb54d392279d You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html