From: Thomas Monjalon <thomas@monjalon.net>
To: Jake Freeland <jfree@freebsd.org>
Cc: Chenbo Xia <chenbox@nvidia.com>,
Nipun Gupta <nipun.gupta@amd.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org
Subject: Re: [PATCH 0/4] BSD PCI Fixes
Date: Tue, 10 Jun 2025 08:24:25 +0200 [thread overview]
Message-ID: <13278384.5MRjnR8RnV@thomas> (raw)
In-Reply-To: <20250506174046.1136711-1-jfree@FreeBSD.org>
06/05/2025 19:40, Jake Freeland:
> Hi there,
>
> The following patchset includes a number of fixes I've made over the
> past year relating to the PCI driver. Most of these changes target
> the FreeBSD platform.
>
> Let me know if you have any feedback. Thanks.
>
> Jake Freeland (4):
> bus/pci: Use force-noreplace flag when mapping PCI resources
> bus/pci/bsd: Map resources at EAL baseaddr
> bus/pci/bsd: Eliminate potential overflow
> bus/pci/bsd: Fix device existence check
Applied, thanks.
prev parent reply other threads:[~2025-06-10 6:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:40 Jake Freeland
2025-05-06 17:40 ` [PATCH 1/4] bus/pci: Use force-noreplace flag when mapping PCI resources Jake Freeland
2025-05-08 11:32 ` Burakov, Anatoly
2025-05-12 14:26 ` Jake Freeland
2025-05-12 14:42 ` Bruce Richardson
2025-05-13 12:54 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 2/4] bus/pci/bsd: Map resources at EAL baseaddr Jake Freeland
2025-05-08 11:31 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 3/4] bus/pci/bsd: Eliminate potential overflow Jake Freeland
2025-05-08 11:28 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 4/4] bus/pci/bsd: Fix device existence check Jake Freeland
2025-05-08 11:27 ` Burakov, Anatoly
2025-06-10 6:24 ` Thomas Monjalon [this message]
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=13278384.5MRjnR8RnV@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=jfree@freebsd.org \
--cc=nipun.gupta@amd.com \
--cc=roretzla@linux.microsoft.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).