From: "Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/5] qat: remove redundant C register keyword
Date: Wed, 5 Sep 2018 10:23:22 +0000 [thread overview]
Message-ID: <CA70B6012E3ADB4184D44E025E5FF01B4CC75A06@HASMSX111.ger.corp.intel.com> (raw)
In-Reply-To: <20180731163059.27085-2-stephen@networkplumber.org>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen
> Hemminger
> Sent: Tuesday, July 31, 2018 6:31 PM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>
> Subject: [dpdk-dev] [PATCH 1/5] qat: remove redundant C register keyword
>
> Modern C compilers ignore the register keyword and do automatic register
> assignment.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
next prev parent reply other threads:[~2018-09-05 10:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 16:30 [dpdk-dev] [PATCH 0/5] remove usage of register keyword in C Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 1/5] qat: remove redundant C register keyword Stephen Hemminger
2018-09-05 10:23 ` Jozwiak, TomaszX [this message]
2018-07-31 16:30 ` [dpdk-dev] [PATCH 2/5] qede: remove register from declaraitons Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 3/5] ark: remove register keyword Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 4/5] mlx5: no need for " Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 5/5] mlx4: remove redunant " Stephen Hemminger
2018-07-31 16:48 ` [dpdk-dev] [PATCH 0/5] remove usage of register keyword in C Adrien Mazarguil
2018-07-31 18:07 ` Stephen Hemminger
2018-08-01 18:03 ` Yongseok Koh
2018-08-01 21:03 ` Stephen Hemminger
2018-08-23 13:07 ` Ferruh Yigit
2018-10-09 9:19 ` Ferruh Yigit
2019-01-31 8:02 ` Tom Barbette
2019-01-31 9:11 ` Bruce Richardson
2019-01-31 9:39 ` Tom Barbette
2019-01-31 17:34 ` Wiles, Keith
2018-08-01 10:18 ` Matan Azrad
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=CA70B6012E3ADB4184D44E025E5FF01B4CC75A06@HASMSX111.ger.corp.intel.com \
--to=tomaszx.jozwiak@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).