On Tue, Oct 17, 2017 at 02:11:47PM +0100, Bruce Richardson wrote:
> On Tue, Oct 17, 2017 at 12:58:32PM +0100, Luca Boccassi wrote:
> > On Tue, 2017-10-17 at 11:41 +0100, Bruce Richardson wrote:
> > > With the large number of changes in 17.11-rc1, the dpdk-next-build
> > > patches would no longer ap
On Tue, Oct 17, 2017 at 12:58:32PM +0100, Luca Boccassi wrote:
> On Tue, 2017-10-17 at 11:41 +0100, Bruce Richardson wrote:
> > With the large number of changes in 17.11-rc1, the dpdk-next-build
> > patches would no longer apply and compile cleanly on top of the main
> > tree. To allow next-build t
On Tue, 2017-10-17 at 11:41 +0100, Bruce Richardson wrote:
> With the large number of changes in 17.11-rc1, the dpdk-next-build
> patches would no longer apply and compile cleanly on top of the main
> tree. To allow next-build to be rebased on top of master, the changes
> listed below needed to be
With the large number of changes in 17.11-rc1, the dpdk-next-build
patches would no longer apply and compile cleanly on top of the main
tree. To allow next-build to be rebased on top of master, the changes
listed below needed to be made to the code.
NOTE: appart from the last patch which may be ke
4 matches
Mail list logo