From: Stephen Hemminger <stephen@networkplumber.org>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 4/4] drivers: use macro to embed information in binaries
Date: Tue, 15 Apr 2025 17:05:17 -0700 [thread overview]
Message-ID: <20250415170517.6a7b37b4@hermes.local> (raw)
In-Reply-To: <1744680096-17683-5-git-send-email-andremue@linux.microsoft.com>
On Mon, 14 Apr 2025 18:21:36 -0700
Andre Muezerie <andremue@linux.microsoft.com> wrote:
> diff --git a/drivers/baseband/acc/rte_acc100_pmd.c b/drivers/baseband/acc/rte_acc100_pmd.c
> index b7f02f56e1..a4cbe6f42f 100644
> --- a/drivers/baseband/acc/rte_acc100_pmd.c
> +++ b/drivers/baseband/acc/rte_acc100_pmd.c
> @@ -4082,9 +4082,9 @@ static struct rte_pci_driver acc100_pci_vf_driver = {
> .drv_flags = RTE_PCI_DRV_NEED_MAPPING
> };
>
> -RTE_PMD_REGISTER_PCI(ACC100PF_DRIVER_NAME, acc100_pci_pf_driver);
> +RTE_PMD_REGISTER_PCI(ACC100PF_DRIVER_NAME, acc100_pci_pf_driver, __LINE__);
Rather than changing so many drivers, can't you just use __LINE__ in the macro?
next prev parent reply other threads:[~2025-04-16 0:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 19:39 [PATCH 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-11 19:39 ` [PATCH 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-11 19:39 ` [PATCH 2/4] buildtools: use " Andre Muezerie
2025-04-11 20:07 ` Dmitry Kozlyuk
2025-04-11 19:39 ` [PATCH 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-11 20:09 ` Dmitry Kozlyuk
2025-04-11 19:39 ` [PATCH 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-04-15 1:21 ` [PATCH v2 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-15 1:21 ` [PATCH v2 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-15 1:21 ` [PATCH v2 2/4] buildtools: use " Andre Muezerie
2025-04-15 7:44 ` Dmitry Kozlyuk
2025-04-15 14:36 ` Andre Muezerie
2025-04-15 1:21 ` [PATCH v2 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-15 11:19 ` Robin Jarry
2025-04-15 1:21 ` [PATCH v2 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-04-16 0:05 ` Stephen Hemminger [this message]
2025-04-17 17:10 ` Andre Muezerie
2025-04-15 22:31 ` [PATCH v3 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-15 22:31 ` [PATCH v3 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-15 22:31 ` [PATCH v3 2/4] buildtools: use " Andre Muezerie
2025-04-15 22:31 ` [PATCH v3 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-15 22:31 ` [PATCH v3 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-04-16 21:44 ` [PATCH v4 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-16 21:44 ` [PATCH v4 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-06-04 14:13 ` Bruce Richardson
2025-06-04 14:52 ` Andre Muezerie
2025-04-16 21:44 ` [PATCH v4 2/4] buildtools: use " Andre Muezerie
2025-06-04 11:04 ` David Marchand
2025-06-04 13:59 ` Andre Muezerie
2025-04-16 21:44 ` [PATCH v4 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-16 21:44 ` [PATCH v4 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-06-03 1:01 ` [PATCH v4 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-06-04 12:03 ` David Marchand
2025-06-04 13:56 ` Andre Muezerie
2025-06-04 13:50 ` [PATCH v5 " Andre Muezerie
2025-06-04 13:50 ` [PATCH v5 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-06-04 13:50 ` [PATCH v5 2/4] buildtools: use " Andre Muezerie
2025-06-04 13:50 ` [PATCH v5 3/4] usertools: parse strings from PE images Andre Muezerie
2025-06-04 13:50 ` [PATCH v5 4/4] drivers: use macro to embed information in binaries Andre Muezerie
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=20250415170517.6a7b37b4@hermes.local \
--to=stephen@networkplumber.org \
--cc=andremue@linux.microsoft.com \
--cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.