From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 582E43775 for ; Wed, 13 May 2015 10:57:04 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 13 May 2015 01:57:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,420,1427785200"; d="scan'208";a="709467338" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.50]) by fmsmga001.fm.intel.com with SMTP; 13 May 2015 01:57:00 -0700 Received: by (sSMTP sendmail emulation); Wed, 13 May 2015 09:57:00 +0025 Date: Wed, 13 May 2015 09:57:00 +0100 From: Bruce Richardson To: Thomas Monjalon Message-ID: <20150513085659.GA12276@bricha3-MOBL3> References: <1430239000-30881-1-git-send-email-stephen@networkplumber.org> <10038698.H9HDUp8o5h@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10038698.H9HDUp8o5h@xps13> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 0/3] eal: uio irq fixes and enhancements X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2015 08:57:04 -0000 On Tue, May 12, 2015 at 10:02:20PM +0200, Thomas Monjalon wrote: > 2015-04-28 09:36, Stephen Hemminger: > > This set of patches starts out with fixing a regression where > > uio_pci_generic broke link state interrupt, then adds better > > management of PCI config space. > > > > Will leave up to document writers to update various release > > notes and API manuals as they see fit. > > > > Also, needs what ever shared library map file updates which > > maybe required when using dynamic libraries. But that should > > not stop acceptance of this patch set. > > No, an incomplete patch cannot be accepted. > There are several solutions: > - Siobhan and Neil accept to work on doc and .map file > - You provide a good v2 > - Someone else finish this patchset > - The bug remains (not a solution) Merge patch one on it's own to fix the issue? I don't think patch 1 requires any further doc or ABI map file changes, does it? /Bruce