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:   Wed, 24 Apr 2019 09:58:45 -0400
From:   Sven Van Asbroeck <>
To:     "Enrico Weigelt, metux IT consult" <>
Cc:     Linus Walleij <>,
        Lee Jones <>,,
        Andreas Färber <>,, David Lechner <>,,,
        Michal Simek <>,,
        Arnd Bergmann <>,
        Greg KH <>,,,,
        Paul Gortmaker <>,,,
        Stuart Yoder <>,
        "J. Kiszka" <>,,
        Linux Kernel Mailing List <>,
        netdev <>
Subject: Re: [PATCH v11 2/7] anybus-s: support HMS Anybus-S bus

On Wed, Apr 24, 2019 at 6:33 AM Enrico Weigelt, metux IT consult
<> wrote:
> I don't like the idea of name changing *after* this went to mainline
> and people are actually using it. At that point, people might even
> already written their own drivers, so they'd have to change them, too.
> Please let's do that ASAP. It doesn't cost us much at this stage.
> > Greg KH has accepted the v11 patch set, so at this stage we can make
> > changes only by circulating patches on the mailing list.
> @Greg: is that already in your tree ? What do you think about doing
> the name change now ?

Greg KH has already taken the patch set.
If we annoy him too much with this niche subsystem, we run
the very real risk that he'll just throw it out.

So any changes (naming or otherwise) will need to follow
the tried-and-tested method of:
- cycling patches on the mailing list until fully cooked
- maintainer sending cooked patches upstream (i.e. Greg KH)


Powered by blists - more mailing lists