[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210811054917.722bd988@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 11 Aug 2021 05:49:17 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Perches <joe@...ches.com>
Cc: Jonathan Toppins <jtoppins@...hat.com>, netdev@...r.kernel.org,
leon@...nel.org, Jay Vosburgh <j.vosburgh@...il.com>,
Veaceslav Falico <vfalico@...il.com>,
Andy Gospodarek <andy@...yhouse.net>,
"David S. Miller" <davem@...emloft.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 2/2] bonding: combine netlink and console
error messages
On Tue, 10 Aug 2021 20:27:01 -0700 Joe Perches wrote:
> > +#define BOND_NL_ERR(bond_dev, extack, errmsg) do { \
> > + if (extack) \
> > + NL_SET_ERR_MSG(extack, errmsg); \
> > + else \
> > + netdev_err(bond_dev, "Error: %s\n", errmsg); \
> > +} while (0)
> > +
> > +#define SLAVE_NL_ERR(bond_dev, slave_dev, extack, errmsg) do { \
> > + if (extack) \
> > + NL_SET_ERR_MSG(extack, errmsg); \
> > + else \
> > + slave_err(bond_dev, slave_dev, "Error: %s\n", errmsg); \
> > +} while (0)
>
> Ideally both of these would be static functions and not macros.
That may break our ability for NL_SET_ERR_MSG to place strings
back in a static buffer, no?
Powered by blists - more mailing lists