From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f66.google.com (mail-wr1-f66.google.com [209.85.221.66]) by dpdk.org (Postfix) with ESMTP id 867487D05 for ; Thu, 1 Nov 2018 12:25:37 +0100 (CET) Received: by mail-wr1-f66.google.com with SMTP id r10-v6so19728684wrv.6 for ; Thu, 01 Nov 2018 04:25:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:mime-version; bh=+oFvU7HW5afblLImONlPvkjaYsIKkVgPfXwI1mMT1o8=; b=nNFnnghbazEMUiv6MkWR6aCVRL9Em4cOS0UieUmNx4pDSKZK/9Hq0ZkVzdTOdRyFCg nzvyXWoPkSlZL5jaNBiTwMhoe+gNcsCGYIyk2SCSyyfL3AaMn1hChKsuRU20oP85ufjo PsUzwwTQCflYapdJP6ax2HX/g347d6jTitKX/k8r1hgoJI/htdJZTESCXXspdiPyo+ix 0/X3Y5owxayxf4I4DzE+It48nf0ePRGpNmuJ3KJFLrKoqHOjnUAJDlV9fAox0T8+L9OU F7xB06ROsYNdxH8Gsb8pMFuUMDk6jUndOnacGW/t4elzoOE6MXY44+DC6goqbz24jFA3 L2UA== X-Gm-Message-State: AGRZ1gLO3MJVuG07wXQtRCfB/bRG2PQK4yjYNvQZuIR4rfHpZYZeD1lP a4RpUwmDV98QjZh4OZFhO4U= X-Google-Smtp-Source: AJdET5cWT+BnINl9Y8rNocFj23q1FkdsG73eZazgeUj+C8KTqgMskK8Auwh6s8fZ1cyxFJbIJ/bePA== X-Received: by 2002:adf:9563:: with SMTP id 90-v6mr6440702wrs.60.1541071537057; Thu, 01 Nov 2018 04:25:37 -0700 (PDT) Received: from localhost ([2001:1be0:110d:fcfe:70c5:32f6:c5b6:39e6]) by smtp.gmail.com with ESMTPSA id 123-v6sm7360210wmw.14.2018.11.01.04.25.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 01 Nov 2018 04:25:35 -0700 (PDT) Message-ID: <1541071534.4849.1.camel@debian.org> From: Luca Boccassi To: yoursunny Cc: Akhil Goyal , dpdk stable Date: Thu, 01 Nov 2018 11:25:34 +0000 In-Reply-To: References: <20181018083737.16783-1-bluca@debian.org> <20181101111121.5570-1-bluca@debian.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 11:25:37 -0000 On Thu, 2018-11-01 at 07:21 -0400, yoursunny wrote: > Hi Luca >=20 > I didn't manage to apply following commits from upstream to stable > branch > > 16.11: conflict happens. I'm wondering can the authors check the > > following > > list and backport those patches belong to you? > >=20 > > FYI, branch 16.11 is located at tree: > > =C2=A0=C2=A0=C2=A0git://dpdk.org/dpdk-stable > >=20 > > f49d7e9a9=C2=A0=C2=A0Junxiao Shi=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0cry= ptodev: fix pool element size for > > undefined > > operation >=20 >=20 > My commit is irrelevant to DPDK 16.11. I=E2=80=99m fixing a small bug > introduced > after DPDK gains asymmetric crypto feature. Back then DPDK does not > support > assymetric crypto. >=20 > > Yours, Junxiao Hi, Ok, false positive in the selection script, thanks for checking. --=20 Kind regards, Luca Boccassi