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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 59B5DC07E96 for ; Tue, 6 Jul 2021 15:44:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3758A61C1A for ; Tue, 6 Jul 2021 15:44:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232584AbhGFPrA (ORCPT ); Tue, 6 Jul 2021 11:47:00 -0400 Received: from relay.sw.ru ([185.231.240.75]:50264 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231689AbhGFPq5 (ORCPT ); Tue, 6 Jul 2021 11:46:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtuozzo.com; s=relay; h=Content-Type:Mime-Version:Message-Id:Subject:From :Date; bh=eufNlsgVDeF1QiogE9FqoCT8BtOHfePU9jT21zZOqao=; b=nZ6h3TkyoQvx+6lpyku dVT6Kt/JtSiSBDuyzK1mZGHl2prJ55Peo2l7v4Mon3m4RFcfWvDb4j5BGJbvA8Arv6xSznPpEI+kx ayQKzVMTadXUiSZ00FzVFaCBQPp8VJOFUd7N+pUVeQf+kWq52TTpjkDwqmMjHHUnLI6vNjfh8Vs=; Received: from [192.168.15.247] (helo=mikhalitsyn-laptop) by relay.sw.ru with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1m0nF9-0035dD-U2; Tue, 06 Jul 2021 18:44:15 +0300 Date: Tue, 6 Jul 2021 18:44:15 +0300 From: Alexander Mikhalitsyn To: Stephen Hemminger Cc: netdev@vger.kernel.org, David Ahern , Andrei Vagin , Alexander Mikhalitsyn Subject: Re: [PATCHv4 iproute2] ip route: ignore ENOENT during save if RT_TABLE_MAIN is being dumped Message-Id: <20210706184415.baf59983a9cb5de56050389c@virtuozzo.com> In-Reply-To: <20210706083407.76deb4c0@hermes.local> References: <20210625104441.37756-1-alexander.mikhalitsyn@virtuozzo.com> <20210629155116.23464-1-alexander.mikhalitsyn@virtuozzo.com> <20210706083407.76deb4c0@hermes.local> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, 6 Jul 2021 08:34:07 -0700 Stephen Hemminger wrote: > On Tue, 29 Jun 2021 18:51:15 +0300 > Alexander Mikhalitsyn wrote: > > > + const struct rtnl_dump_filter_arg a[2] = { > > + { .filter = filter, .arg1 = arg1, > > + .errhndlr = errhndlr, .arg2 = arg2, .nc_flags = nc_flags, }, > > + { .filter = NULL, .arg1 = NULL, > > + .errhndlr = NULL, .arg2 = NULL, .nc_flags = 0, }, > > }; > > I am OK with this as is. But you don't need to add initializers for fields > that are 0/NULL (at least in C). Sure, I've made such explicit initializations just because in original rtnl_dump_filter_nc() we already have them. Do I need to resend with fixed initializations? ;) > > So could be: > const struct rtnl_dump_filter_arg a[] = { > { .filter = filter, .arg1 = arg1, > .errhndlr = errhndlr, .arg2 = arg2, .nc_flags = nc_flags, }, > { }, > }; Thanks, Alex