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]
Date:   Mon, 23 May 2022 12:37:01 -0700
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Greg KH <gregkh@...uxfoundation.org>, tj@...nel.org,
        akpm@...ux-foundation.org, jeyu@...nel.org, shuah@...nel.org,
        bvanassche@....org, dan.j.williams@...el.com, joe@...ches.com,
        keescook@...omium.org, rostedt@...dmis.org, minchan@...nel.org,
        linux-spdx@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 3/6] selftests: add tests_sysfs module

On Sun, May 22, 2022 at 05:06:44PM +0200, Thomas Gleixner wrote:
> On Sun, May 22 2022 at 16:47, Greg KH wrote:
> > On Sun, May 22, 2022 at 04:37:19PM +0200, Thomas Gleixner wrote:
> >> On Fri, Dec 03 2021 at 16:29, Greg KH wrote:
> >> 
> >> While I agree that we want to keep the number of licenses as small as
> >> possible, we cannot really dictate which dual licensing options a
> >> submitter selects unless the license is GPL-2.0-only incompatible, which
> >> copyleft-next is not.
> >> 
> >> Can we just get over this, add the license with the SPDX identifier and
> >> move on?
> >
> > From what I recall, I had technical reasons I didn't take this series,
> > but that was a long time ago and I would be glad to review it again if
> > it were rebased and resubmitted after the next merge window is closed.
> 
> The license addition and the SPDX identifier cleanup should be seperated
> from the new test code which was part of the series.

I'll send a re-spin after the merge window and split this up.

And FWIW, AFAICT I addressed all the comments, so I can resend after
the spdx stuff gets merged so to make the series easier to read /
review.

  Luis

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ