All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH 2/2] eal/bsd: fix the read operation on PCI configuration space
Date: Mon, 8 May 2017 10:47:20 +0100	[thread overview]
Message-ID: <20170508094720.GB34348@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20170507133334.16219-3-tiwei.bie@intel.com>

On Sun, May 07, 2017 at 01:33:34PM +0000, Tiwei Bie wrote:
> Some drivers (such as virtio) may need to read more than 4 bytes
> data from PCI configuration space via rte_eal_pci_read_config().
> But it will return with an error on FreeBSD when the expected
> data length is bigger than the size of pi.pi_data whose type is
> u_int32_t. This patch removes this limitation.
> 
> Fixes: 632b2d1deeed ("eal: provide functions to access PCI config")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2017-05-08  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 13:33 [PATCH 0/2] various fixes for eal/bsd Tiwei Bie
2017-05-07 13:33 ` [PATCH 1/2] eal/bsd: fix ioport write operation Tiwei Bie
2017-05-08  8:55   ` Bruce Richardson
2017-05-08  9:07     ` Tiwei Bie
2017-05-08  9:46       ` Bruce Richardson
2017-05-07 13:33 ` [PATCH 2/2] eal/bsd: fix the read operation on PCI configuration space Tiwei Bie
2017-05-08  9:47   ` Bruce Richardson [this message]
2017-05-10 13:58 ` [PATCH 0/2] various fixes for eal/bsd Thomas Monjalon

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=20170508094720.GB34348@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.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 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.