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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ2ouaymVp1Hw1ptOu+N0z+YLFLOz9JQVangHmrFApHriA09tg@mail.gmail.com>
Date:   Thu, 6 Dec 2018 09:59:20 +0100
From:   Jouke Witteveen <j.witteveen@...il.com>
To:     davem@...emloft.net
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] net: linkwatch: send change uevent on link changes

On Thu, Dec 6, 2018 at 1:34 AM David Miller <davem@...emloft.net> wrote:
>
> From: Jouke Witteveen <j.witteveen@...il.com>
> Date: Wed, 5 Dec 2018 23:38:17 +0100
>
> > Can you elaborate a bit? I may not be aware of the policy you have in
> > mind.
>
> When we have a user facing interface to do something, we don't create
> another one unless it is absolutely, positively, unavoidable.

Obviously, if I would have known this I would not have gone through
the trouble of investigating and proposing this patch. It was an
honest attempt at making the kernel better.
Where could I have found this policy? I have looked on kernel.org/doc,
but couldn't find it.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ