From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] common/idpf: remove unnecessary compile option
Date: Wed, 26 Apr 2023 07:12:08 +0000 [thread overview]
Message-ID: <DM4PR11MB5994338DEA017EC5123CA28CD7659@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230424092348.726583b1@hermes.local>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Tuesday, April 25, 2023 12:24 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: Xing, Beilei <beilei.xing@intel.com>; dev@dpdk.org
> Subject: Re: [PATCH] common/idpf: remove unnecessary compile option
>
> On Mon, 24 Apr 2023 18:47:00 -0400
> Qi Zhang <qi.z.zhang@intel.com> wrote:
>
> > Remove compile option "__KERNEL" which should not be considered in
> > DPDK. Also only #include <rte_xxx> in idpf_osdep.h.
> >
> > Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
>
> This will cause some warnings in DPDK build depending on compiler version
> and flags. You need to leave the fallthrough comment or use one of the
> other fallthrough annotations.
no intention of removing that comment, as it serves to assist the reader.
It's good to learn that it has also helped to resolve the compiler warning - thank you for bringing this to my attention.
next prev parent reply other threads:[~2023-04-26 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 22:47 Qi Zhang
2023-04-24 16:23 ` Stephen Hemminger
2023-04-24 17:29 ` Tyler Retzlaff
2023-04-24 17:41 ` Stephen Hemminger
2023-04-26 7:12 ` Zhang, Qi Z [this message]
2023-04-26 15:38 ` [PATCH v2] " Qi Zhang
2023-04-27 9:36 ` Xing, Beilei
2023-04-27 9:53 ` Zhang, Qi Z
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=DM4PR11MB5994338DEA017EC5123CA28CD7659@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).