DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: "Jerin Jacob" <jerinjacobk@gmail.com>,
	dev@dpdk.org, "Dmitry Kozlyuk" <dmitry.kozliuk@gmail.com>,
	"Gaëtan Rivet" <grive@u256.net>
Subject: Re: [dpdk-dev] [PATCH] doc: announce PCI resources map API removal
Date: Thu, 06 Aug 2020 01:21:06 +0200	[thread overview]
Message-ID: <3679442.LJigX5mhQc@thomas> (raw)
In-Reply-To: <20200804112013.vvwdyphqfmbn3ase@u256.net>

04/08/2020 13:20, Gaëtan Rivet:
> On 04/08/20 14:22 +0530, Jerin Jacob wrote:
> > On Tue, Aug 4, 2020 at 2:18 PM David Marchand <david.marchand@redhat.com> wrote:
> > >
> > > The PCI resources map API (pci_map_resource/pci_unmap_resource) was
> > > imposing use of Unix mmap flags while it does not make sense on Windows.
> > > This API was only used to internally setup PCI devices in the PCI bus
> > > driver and has no known external users.
> > >
> > > Announce its removal in 20.11 with its associated structures.
> > >
> > > The workaround implemented in the commit 9d2b24593724 ("pci: keep API
> > > compatibility with mmap values") will be removed at the same time.
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Jerin Jacob <jerinj@marvell.com>
> Acked-by: Gaetan Rivet <grive@u256.net>
Acked-by: Thomas Monjalon <thomas@monjalon.net>

Applied, thanks



      reply	other threads:[~2020-08-05 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  8:47 David Marchand
2020-08-04  8:52 ` Jerin Jacob
2020-08-04 11:20   ` Gaëtan Rivet
2020-08-05 23:21     ` 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=3679442.LJigX5mhQc@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=grive@u256.net \
    --cc=jerinjacobk@gmail.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).