From: Jakub Kicinski <kuba@kernel.org>
To: "Kamil Horák - 2N" <kamilh@axis.com>
Cc: <florian.fainelli@broadcom.com>,
<bcm-kernel-feedback-list@broadcom.com>, <andrew@lunn.ch>,
<hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net v3 1/1] net: phy: bcm54811: Fix GMII/MII/MII-Lite selection
Date: Mon, 13 Oct 2025 17:43:22 -0700 [thread overview]
Message-ID: <20251013174322.1cbffbb8@kernel.org> (raw)
In-Reply-To: <20251009130656.1308237-2-kamilh@axis.com>
On Thu, 9 Oct 2025 15:06:56 +0200 Kamil Horák - 2N wrote:
> Signed-off-by: Kamil Horák - 2N <kamilh@axis.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@example.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@example.com>
See:
https://www.kernel.org/doc/html/next/process/submitting-patches.html#the-canonical-patch-format
next prev parent reply other threads:[~2025-10-14 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 13:06 [PATCH net v3 0/1] net: phy: bcm54811: Fix GMII/MII/MII-Lite selection Kamil Horák - 2N
2025-10-09 13:06 ` [PATCH net v3 1/1] " Kamil Horák - 2N
2025-10-13 22:27 ` Florian Fainelli
2025-10-14 0:43 ` Jakub Kicinski [this message]
2025-10-14 1:10 ` [PATCH net v3 0/1] " patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251013174322.1cbffbb8@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=kamilh@axis.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).