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: <20251013174322.1cbffbb8@kernel.org>
Date: Mon, 13 Oct 2025 17:43:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Kamil Horák - 2N <kamilh@...s.com>
Cc: <florian.fainelli@...adcom.com>,
 <bcm-kernel-feedback-list@...adcom.com>, <andrew@...n.ch>,
 <hkallweit1@...il.com>, <linux@...linux.org.uk>, <davem@...emloft.net>,
 <edumazet@...gle.com>, <pabeni@...hat.com>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net v3 1/1] net: phy: bcm54811: Fix GMII/MII/MII-Lite
 selection

On Thu, 9 Oct 2025 15:06:56 +0200 Kamil Horák - 2N wrote:
> Signed-off-by: Kamil Horák - 2N <kamilh@...s.com>

If "2N" is a company name - going forward please use the preferred
format which is round brackets:

Quoting documentation:

  The canonical patch format
  --------------------------

  From Line
  ^^^^^^^^^
  
  The ``from`` line must be the very first line in the message body,
  and has the form:
  
          From: Patch Author <author@...mple.com>
  
  The ``from`` line specifies who will be credited as the author of the
  patch in the permanent changelog.  If the ``from`` line is missing,
  then the ``From:`` line from the email header will be used to determine
  the patch author in the changelog.
  
  The author may indicate their affiliation or the sponsor of the work
  by adding the name of an organization to the ``from`` and ``SoB`` lines,
  e.g.:
  
  	From: Patch Author (Company) <author@...mple.com>
  
See:
https://www.kernel.org/doc/html/next/process/submitting-patches.html#the-canonical-patch-format

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ