From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-f67.google.com (mail-wm1-f67.google.com [209.85.128.67]) by dpdk.org (Postfix) with ESMTP id 6EA094F93 for ; Sun, 16 Sep 2018 21:23:18 +0200 (CEST) Received: by mail-wm1-f67.google.com with SMTP id y139-v6so7095952wmc.2 for ; Sun, 16 Sep 2018 12:23:18 -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=fYorWrCCtUm7kaSbQCJxMVEfnepMaa+FawPwxNdSYdY=; b=lpiM5+0kKRfGzZzkrtPmv0TaTS+AW5EyFvszJebt+8M07RsO97i3sbR9aqts5f217T F0nrkuxOiRRH4GiA7aExhrOjfAYBYhtjZqgXXsoerUsYw4zaHB8yRj3ihMuxNoN4kFPb vGgR82A+ECVkM+vpLhF2YNgE+FsXpDJUPIqxhYRYHuBflFLt8QBw8xZaG/n8eui0kRx3 Iy4UHIGUiCP8hGsDgPL1uRf7PVqvxPBI+lRO/DhAQOmon1IOsYOGJWhgjV+slGYa+Daw s9Lr7aC0QQy0PX0JF1CKCxKmDgQbIdNZQtbYu6eLPj8wtHKx7JVWZT+xF/LbQEBSAQ4G dZgg== X-Gm-Message-State: APzg51AWgY49/GpRCxZNjqZbt5f9GNTFZtAZ//1/PJDByZ+pv0vozGVB zZF9YcfqKS1tSQSHYutVWI4= X-Google-Smtp-Source: ANB0VdYfbjiHlx4SZ2+caTezCC1WjhBmQCL717zU/UCEZI9owimkBu6b0VLb7qWvWeYCMvGGFGEU1A== X-Received: by 2002:a1c:5c4:: with SMTP id 187-v6mr9122854wmf.10.1537125797837; Sun, 16 Sep 2018 12:23:17 -0700 (PDT) Received: from localhost ([2a01:4b00:f419:6f00:95ec:3dbf:2198:6b50]) by smtp.gmail.com with ESMTPSA id u127-v6sm4349890wmf.48.2018.09.16.12.23.16 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 16 Sep 2018 12:23:16 -0700 (PDT) Message-ID: <1537125796.25823.3.camel@debian.org> From: Luca Boccassi To: Honnappa Nagarahalli , Thomas Monjalon Cc: "stable@dpdk.org" , Yongseok Koh , nd Date: Sun, 16 Sep 2018 20:23:16 +0100 In-Reply-To: References: <1535913120-22426-1-git-send-email-honnappa.nagarahalli@arm.com> <3669CA39-FCDC-4138-8B8F-1BD629A73197@mellanox.com> <4099711.yRKz0YspiK@xps> 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] [PATCH v2] build: enable Arm NEON flags when __aarch64__ is defined 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: Sun, 16 Sep 2018 19:23:18 -0000 On Sun, 2018-09-16 at 14:40 +0000, Honnappa Nagarahalli wrote: >=20 > -----Original Message----- > From: Thomas Monjalon =C2=A0 > Sent: Sunday, September 16, 2018 3:16 AM > To: Honnappa Nagarahalli > Cc: stable@dpdk.org; Yongseok Koh ; nd m> > Subject: Re: [dpdk-stable] [PATCH v2] build: enable Arm NEON flags > when __aarch64__ is defined >=20 > 04/09/2018 20:53, Yongseok Koh: > >=20 > > > On Sep 4, 2018, at 11:41 AM, Yongseok Koh > > > wrote: > > >=20 > > > > On Sep 3, 2018, at 1:25 AM, Honnappa Nagarahalli > > > rahalli@arm.com> wrote: > > > > > I didn't check out the details yet but a quick question. > > > > > Do you want me to include this patch in 17.11.4? > > > > >=20 > > > > > Yes, please include. > > > >=20 > > > > I didn't realized that this is fixing the meson build. > > > > 17.11 doesn't have that. > > > >=20 > > > > Thanks, > > > > Yongseok > > > >=20 > > > > It has a fix for the make build as well. Does it mean, it needs > > > > to be a different patch? > > >=20 > > > I could've applied the second hunk but actually it was one > > > minute=C2=A0 > > > before the release of 17.11.4. I'm sorry that I had to skip this > > > patch for the release. > > >=20 > > > But, I've applied it (the second hunk only) to the stable/17.11 > > > tree today. > > > Please check it out and let me know if there's an issue.=C2=A0=C2=A0T= his > > > will=C2=A0 > > > be included in 17.11.5 (ETA is Nov). > > >=20 > > > FYI, the most favorable way is that you send patches with > > > '[PATCH=C2=A0 > > > 17.11]' prefix based on the latest stable/17.11 so that it is > > > never forgotten. > >=20 > > One more FYI. > > Even though this was sent to stable (without dev@dpdk.org), as you=C2= =A0 > > have also sent a same patch[1] to dev@dpdk.org, this will be > > queued=C2=A0 > > for next stable releases anyway once it is merged to dpdk/master. > >=20 > > [1] https://mails.dpdk.org/archives/dev/2018-September/110713.html >=20 > There is no reason to send this patch specifically to stable@dpdk.org > . > The usual process is to wait the patch is applied on master, then > backport it on stable branches. >=20 > My apologies. I seem to have misunderstood a comment (http://mails.dp > dk.org/archives/dev/2018-August/110342.html). Do we send patches to > stable@dpdk.org only when the patches are backported? In the commit message itself, add: Cc: stable@dpdk.org in the text, and it will be considered automatically for backporting once merged in master. Only send directly to stable when asked, or when a bug affects only a stable release but not master (and explain why). --=20 Kind regards, Luca Boccassi