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 X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B15FC43381 for ; Wed, 20 Feb 2019 16:35:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 29C222183F for ; Wed, 20 Feb 2019 16:35:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="pmcThLtu" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726902AbfBTQfM (ORCPT ); Wed, 20 Feb 2019 11:35:12 -0500 Received: from mail-qk1-f193.google.com ([209.85.222.193]:40615 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725895AbfBTQfM (ORCPT ); Wed, 20 Feb 2019 11:35:12 -0500 Received: by mail-qk1-f193.google.com with SMTP id h28so2343403qkk.7 for ; Wed, 20 Feb 2019 08:35:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:message-id:from:to:cc:subject:in-reply-to:references :mime-version:content-disposition:content-transfer-encoding; bh=Y0hO1GXOuXivUtZFgU6Mrh5OFhwey2sGeaGkwghhOVM=; b=pmcThLtuekqDSKySQW+M+NRDWmeTDYlXcFnxC48jGgW/+r1MDjoZ2++scSWz+vgszG +M6nxhjhaNt3VS+6wkCEjmw096iNtM2N/1kDDyeqRNpF1HDIZ1tEsK70wd5+UehoqPRw tHdkMWg/FA/6TJpr2vJhHT0JXA0fwUFTJ87SInbZrbhW+d0Ryei0r219dNiGaXKmP89/ FnjRcroEMbuLWjeHWQJF5Yin3yzuhbfpUER1C5mWITtfgplHNF6uGvyc7oj58rgKlows mqW8PqBlm88xoBdtvV6djZRMUyR75qM/dI3GemBHpLEr3Uzh85VOdIiLmSriPG5SFCNq PSEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:from:to:cc:subject:in-reply-to :references:mime-version:content-disposition :content-transfer-encoding; bh=Y0hO1GXOuXivUtZFgU6Mrh5OFhwey2sGeaGkwghhOVM=; b=g9s03/nllRpYP3MgJ6ZoPyMFc4FSBxpqXxfF7Z9Hk5LVO2smpkjTQFeuCokWzvgT+s eq6R9gqXEWOf830WAO35jvzprk64BqjwH0oYMt58u55uqIs6KvuFNf7QRYqgk2oEm+/C GO/RYBKjGtmhHGtJS3AQnTgS0sZDl1Fl5M352ljJ1nuh6Ke5dOAG5Wn685YoikVn1PZY d/ii9RsOpJKKq2qW+4v/UJ4rDdCRpRu2sxOXreJDkacEdR5IJYGp62iMB9rEw4bvuIEj vDoAZ5+GVwGQqEt9iPUouCg/HsTog3JOVs4I7X5rB1V1ZWBfBfQAbCBN6b74lrfVS0W0 Db6Q== X-Gm-Message-State: AHQUAubJludnvZgcIgZfU3ZaxZAxSuCsDaDd2/Zql2TEsu+vkJnG+AfA pbyUB7XmNkLl+UMZXHuPIW0= X-Google-Smtp-Source: AHgI3IYQuAWvAQ13LIznRBpr38kipgqtL1rMnfYLW0Pb9bO+X4dPhUG4ehkcNx0jRjtcehLbmCRRog== X-Received: by 2002:a05:620a:122e:: with SMTP id v14mr25372321qkj.105.1550680511524; Wed, 20 Feb 2019 08:35:11 -0800 (PST) Received: from localhost (modemcable249.105-163-184.mc.videotron.ca. [184.163.105.249]) by smtp.gmail.com with ESMTPSA id 81sm10450695qkg.75.2019.02.20.08.35.10 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 20 Feb 2019 08:35:10 -0800 (PST) Date: Wed, 20 Feb 2019 11:35:10 -0500 Message-ID: <20190220113510.GB26057@t480s.localdomain> From: Vivien Didelot To: Russell King - ARM Linux admin Cc: netdev@vger.kernel.org, stephen@networkplumber.org Subject: Re: [PATCH iproute2] bridge: make mcast_flood description consistent In-Reply-To: <20190220000528.pl6uc2w3hcxiwb7v@shell.armlinux.org.uk> References: <20190219234738.17009-1-vivien.didelot@gmail.com> <20190220000528.pl6uc2w3hcxiwb7v@shell.armlinux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi Russell, On Wed, 20 Feb 2019 00:05:29 +0000, Russell King - ARM Linux admin wrote: > I'm not sure if it's in the current iproute2, but there is a > discrepency between the arguments for 'bridge' stated in the man page > and the description thereof: > > bridge link set dev DEV [ cost COST ] [ priority PRIO ] [ state STATE > ... > } ] [ learning_sync { on | off } ] [ flood { on | off } ] [ > ^^^^^^^^^^^^^^^^^^ > > vs > > flooding on or flooding off > Controls whether a given port will flood unicast traffic for > which there is no FDB entry. By default this flag is on. > > vs the command actually accepting "flood" not "flooding". I spotted > that in iproute2-4.20.0. I haven't had a chance to generate a patch > that yet and work out how to submit it, but thanks for leading the > way! You are correct! I've sent a v2. Thank you, Vivien