From: Stephen Hemminger <stephen@networkplumber.org>
To: "Zhang, Yuying" <yuying.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [PATCH v3 13/14] net/i40e: fix whitespace
Date: Fri, 11 Nov 2022 08:48:17 -0800 [thread overview]
Message-ID: <20221111084817.17b177da@hermes.local> (raw)
In-Reply-To: <DM6PR11MB3516D9754E1416F03C0338C68E009@DM6PR11MB3516.namprd11.prod.outlook.com>
On Fri, 11 Nov 2022 06:23:31 +0000
"Zhang, Yuying" <yuying.zhang@intel.com> wrote:
> Hi,
>
> Could you add fix line and Cc: stable@dpdk.org?
> The fix looks good to me.
Whitespace changes don't belong in stable unless they are prerequisite for another change.
next prev parent reply other threads:[~2022-11-11 16:48 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 19:14 [PATCH 00/14] whitespace around keywords Stephen Hemminger
2022-11-09 19:14 ` [PATCH 01/14] eal: fix whitespace Stephen Hemminger
2022-11-09 19:14 ` [PATCH 02/14] cmdline: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 03/14] timer: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 04/14] ip_frag: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 05/14] testpmd: fix whitspace Stephen Hemminger
2022-11-09 19:14 ` [PATCH 06/14] test: fix whitespace Stephen Hemminger
2022-11-09 19:14 ` [PATCH 07/14] examples/qos_sched: " Stephen Hemminger
2022-11-09 19:28 ` Dumitrescu, Cristian
2022-11-09 19:14 ` [PATCH 08/14] examples/vhost: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 09/14] l3fwd: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 10/14] examples: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 11/14] bus/pci: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 12/14] net/e1000: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 13/14] net/i40e: " Stephen Hemminger
2022-11-09 19:14 ` [PATCH 14/14] net/bnx2x: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 00/14] whitespace after keywords Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 01/14] eal: fix whitespace Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 02/14] cmdline: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 03/14] timer: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 04/14] ip_frag: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 05/14] testpmd: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 06/14] test: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 07/14] examples/qos_sched: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 08/14] examples/vhost: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 09/14] l3fwd: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 10/14] examples: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 11/14] bus/pci: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 12/14] net/e1000: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 13/14] net/i40e: " Stephen Hemminger
2022-11-09 19:53 ` [PATCH v2 14/14] net/bnx2x: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 00/14] whitespace after keywords Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 01/14] eal: fix whitespace Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 02/14] cmdline: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 03/14] timer: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 04/14] ip_frag: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 05/14] testpmd: " Stephen Hemminger
2022-11-11 6:30 ` Zhang, Yuying
2022-11-11 7:12 ` Zhang, Yuying
2022-11-09 23:24 ` [PATCH v3 06/14] test: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 07/14] examples/qos_sched: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 08/14] examples/vhost: " Stephen Hemminger
2022-11-10 1:48 ` Xia, Chenbo
2022-11-09 23:24 ` [PATCH v3 09/14] l3fwd: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 10/14] examples: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 11/14] bus/pci: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 12/14] net/e1000: " Stephen Hemminger
2022-11-09 23:24 ` [PATCH v3 13/14] net/i40e: " Stephen Hemminger
2022-11-11 6:23 ` Zhang, Yuying
2022-11-11 7:12 ` Zhang, Yuying
2022-11-11 16:48 ` Stephen Hemminger [this message]
2022-11-09 23:24 ` [PATCH v3 14/14] net/bnx2x: " Stephen Hemminger
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=20221111084817.17b177da@hermes.local \
--to=stephen@networkplumber.org \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=yuying.zhang@intel.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).