From: "Lin Ma" <linma@zju.edu.cn>
To: "Markus Elfring" <Markus.Elfring@web.de>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
"Alexander Duyck" <alexander.h.duyck@intel.com>,
"Daniel Machon" <daniel.machon@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Peter P Waskiewicz Jr" <peter.p.waskiewicz.jr@intel.com>,
"Petr Machata" <petrm@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: dcb: choose correct policy to parse DCB_ATTR_BCN
Date: Tue, 1 Aug 2023 09:34:17 +0800 (GMT+08:00) [thread overview]
Message-ID: <3d159780.f2fb6.189aebb4a18.Coremail.linma@zju.edu.cn> (raw)
In-Reply-To: <fbda76a9-e1f3-d483-ab3d-3c904c54a5db@web.de>
Hello Markus,
>
> …
> > This patch use correct dcbnl_bcn_nest policy to parse the
> > tb[DCB_ATTR_BCN] nested TLV.
>
> Are imperative change descriptions still preferred?
>
> See also:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.5-rc3#n94
>
> Regards,
> Markus
Yeah, thanks for reminding me. I haven't been paying attention to that and I will remember this ever since. :D
Regards,
Lin
next prev parent reply other threads:[~2023-08-01 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 4:52 [PATCH net v1] " Lin Ma
2023-07-31 10:00 ` Simon Horman
[not found] ` <fbda76a9-e1f3-d483-ab3d-3c904c54a5db@web.de>
2023-08-01 1:34 ` Lin Ma [this message]
2023-08-01 5:46 ` [PATCH net] " Dan Carpenter
2023-08-01 6:01 ` Lin Ma
[not found] ` <ed7020cb-cee5-16af-55f1-f1adac08f1b6@web.de>
2023-08-01 10:28 ` net: dcb: Communication challenges for patch reviews? Dan Carpenter
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=3d159780.f2fb6.189aebb4a18.Coremail.linma@zju.edu.cn \
--to=linma@zju.edu.cn \
--cc=Markus.Elfring@web.de \
--cc=alexander.h.duyck@intel.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=petrm@nvidia.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
all inboxes | Powered by JetHome®