[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210210121935.4ia5ubavws2hz5jj@lion.mk-sys.cz>
Date: Wed, 10 Feb 2021 13:19:35 +0100
From: Michal Kubecek <mkubecek@...e.cz>
To: Danielle Ratson <danieller@...dia.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"andrew@...n.ch" <andrew@...n.ch>, mlxsw <mlxsw@...dia.com>
Subject: Re: [PATCH ethtool v2 1/5] ethtool: Extend ethtool link modes
settings uAPI with lanes
On Wed, Feb 10, 2021 at 12:06:04PM +0000, Danielle Ratson wrote:
> > When updating the UAPI header copies, please do it in a separate
> > commit which updates the whole uapi/ subdirectory to the state of a
> > specific kernel commit. You can use the script at
> >
> > https://www.kernel.org/pub/software/network/ethtool/ethtool-import-uapi
> >
> > It expects the LINUX_GIT environment variable to point to your local
> > git repository with kernel tree and takes one argument identifying
> > the commit you want to import the uapi headers from (commit id, tag
> > or branch name can be used). In your case, net-next would be the
> > most likely choice.
>
> Should I use the commit in net-next that I added it uapi headers, or
> generally the last commit of net-next?
That's up to you, I'm fine with either. The important point is to have
a consistent snapshot of all copied (and sanitized) uapi headers.
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists