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: <ZN65iiRiSLmXz89k@casper.infradead.org>
Date:   Fri, 18 Aug 2023 01:21:30 +0100
From:   Matthew Wilcox <willy@...radead.org>
To:     Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc:     Giulio Benetti <giulio.benetti@...ettiengineering.com>,
        Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/1] docs: submitting-patches: Add Sponsored-by tag
 to give credits to who sponsored the patch

On Fri, Aug 18, 2023 at 02:23:48AM +0300, Laurent Pinchart wrote:
> Just adding one data point here, without judging on the merits of this
> proposal. I've been requested previously by customers to increase their
> visibility in the kernel development statistics, and the way we found to
> do so was to sign-off patches with
> 
> Laurent Pinchart <laurent.pinchart+customer@...asonboard.com>
> 
> (where "customer" is to be replaced with the customer name).

I quite like Sponsored-by: but yet another approach could be the
same as that used by those of us whole use personal email addresses
while being employed by someone.  So my SoB is:

Matthew Wilcox (Oracle) <willy@...radead.org>

but you might have (eg)

Laurent Pinchard (Coca-Cola) <laurent.pinchart@...asonboard.com>

and then when working for another sponsor:

Laurent Pinchard (Ford) <laurent.pinchart@...asonboard.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ