From: Ronak Doshi <doshir@vmware.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Jochen Behrens <jbehrens@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH next 4/7] vmxnet3: add command to set ring buffer sizes
Date: Wed, 26 Apr 2023 17:27:23 +0000 [thread overview]
Message-ID: <900F6434-CE10-4FB7-B370-22D67D0B2F33@vmware.com> (raw)
In-Reply-To: <b4b8c6cd-1586-d64c-6ed4-e22fba4dc616@amd.com>
On 4/26/23, 9:58 AM, "Ferruh Yigit" <ferruh.yigit@amd.com <mailto:ferruh.yigit@amd.com>> wrote:
> As far as I can see these "vmware_pack_begin.h" & "vmware_pack_end.h"
> has only file license comment, and I can see this is used in a few other
> type declaration.
>
> What is the reasoning behind using these headers?
This has been the case since driver was added to dpdk. The information is present in README.
I did not want to change the format being used for the declarations in the driver.
Thanks,
Ronak
next prev parent reply other threads:[~2023-04-26 19:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 16:26 [PATCH next 0/7] vmxnet3: upgrade to version 7 Ronak Doshi
2023-04-12 16:26 ` [PATCH next 1/7] vmxnet3: prepare for version 7 changes Ronak Doshi
2023-04-26 16:58 ` Ferruh Yigit
2023-04-12 16:26 ` [PATCH next 2/7] vmxnet3: add support for capability registers Ronak Doshi
2023-04-26 16:55 ` Ferruh Yigit
2023-04-12 16:26 ` [PATCH next 3/7] vmxnet3: add support for large passthrough BAR register Ronak Doshi
2023-04-12 16:26 ` [PATCH next 4/7] vmxnet3: add command to set ring buffer sizes Ronak Doshi
2023-04-26 16:58 ` Ferruh Yigit
2023-04-26 17:27 ` Ronak Doshi [this message]
2023-04-27 8:50 ` Ferruh Yigit
2023-04-27 15:59 ` Ronak Doshi
2023-05-03 10:03 ` Ferruh Yigit
2023-04-12 16:26 ` [PATCH next 5/7] vmxnet3: limit number of TXDs used for TSO packet Ronak Doshi
2023-04-12 16:26 ` [PATCH next 6/7] vmxnet3: avoid updating rxprod register frequently Ronak Doshi
2023-04-12 16:26 ` [PATCH next 7/7] vmxnet3: update to version 7 Ronak Doshi
2023-04-26 16:54 ` [PATCH next 0/7] vmxnet3: upgrade " Ferruh Yigit
2023-04-26 18:15 ` Ferruh Yigit
2023-04-26 18:33 ` Ronak Doshi
2023-04-27 9:15 ` Ferruh Yigit
2023-04-28 7:05 ` Ronak Doshi
2023-05-03 10:05 ` Ferruh Yigit
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=900F6434-CE10-4FB7-B370-22D67D0B2F33@vmware.com \
--to=doshir@vmware.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jbehrens@vmware.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).