netdev - Re: [PATCH iproute-next v3 2/3] lib: Introduce ppp protocols

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 29 Jul 2022 09:00:52 -0600
From:   David Ahern <dsahern@...il.com>
To:     "Drewek, Wojciech" <wojciech.drewek@...el.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Cc:     "stephen@...workplumber.org" <stephen@...workplumber.org>,
        "gnault@...hat.com" <gnault@...hat.com>
Subject: Re: [PATCH iproute-next v3 2/3] lib: Introduce ppp protocols

On 7/29/22 2:59 AM, Drewek, Wojciech wrote:
> What is the standard procedure in such situation?
> Should I create separate commit with uapi update, should
> I not include uapi changes and ask you to update it?

I always pull uapi files from a kernel header sync point. If a patch or
set contains a uapi update, it is removed before applying.

If uapi changes are included in a set, a separate patch file is best. I
can ignore it and apply the rest without modifying patch files.