From: Jakub Kicinski <kuba@kernel.org>
To: David Thompson <davthompson@nvidia.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"cai.huoqing@linux.dev" <cai.huoqing@linux.dev>,
"brgl@bgdev.pl" <brgl@bgdev.pl>, Liming Sun <limings@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>
Subject: Re: [PATCH net v1] mlxbf_gige: compute MDIO period based on i1clk
Date: Thu, 1 Sep 2022 08:50:47 -0700 [thread overview]
Message-ID: <20220901085047.37a71af4@kernel.org> (raw)
In-Reply-To: <DM6PR12MB553413FEE0C3C357010CDBB3C77B9@DM6PR12MB5534.namprd12.prod.outlook.com>
On Thu, 1 Sep 2022 15:32:13 +0000 David Thompson wrote:
> > Hm, why did you repost this?
>
> I reposted because the first post failed the "netdev/cc_maintainers" test:
>
> netdev/cc_maintainers fail 1 blamed authors not CCed: limings@nvidia.com; 1 maintainers not CCed: limings@nvidia.com
>
> In the second post I included "limings@nvidia.com" .
I see.. FWIW the checks are not 100% accurate, I would have ignored that
one. We're a little more lax about CCing people from the same company.
Next time please put the reason in the changelog under the ---
separator, to avoid any confusion and delays. Thanks!
next prev parent reply other threads:[~2022-09-01 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 15:59 [PATCH net v1] mlxbf_gige: compute MDIO period based on i1clk David Thompson
2022-08-27 1:49 ` Jakub Kicinski
2022-09-01 15:32 ` David Thompson
2022-09-01 15:50 ` Jakub Kicinski [this message]
2022-08-31 19:20 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-08-24 22:32 David Thompson
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=20220901085047.37a71af4@kernel.org \
--to=kuba@kernel.org \
--cc=asmaa@nvidia.com \
--cc=brgl@bgdev.pl \
--cc=cai.huoqing@linux.dev \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=limings@nvidia.com \
--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).