From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Yongseok Koh <yskoh@mellanox.com>, nd <nd@arm.com>
Subject: Re: [dpdk-stable] [PATCH v2] build: enable Arm NEON flags when __aarch64__ is defined
Date: Sun, 16 Sep 2018 14:40:11 +0000 [thread overview]
Message-ID: <AM0PR08MB366707F4FC7488D472D815B3981F0@AM0PR08MB3667.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <4099711.yRKz0YspiK@xps>
-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Sunday, September 16, 2018 3:16 AM
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: stable@dpdk.org; Yongseok Koh <yskoh@mellanox.com>; nd <nd@arm.com>
Subject: Re: [dpdk-stable] [PATCH v2] build: enable Arm NEON flags when __aarch64__ is defined
04/09/2018 20:53, Yongseok Koh:
>
> > On Sep 4, 2018, at 11:41 AM, Yongseok Koh <yskoh@mellanox.com> wrote:
> >
> >> On Sep 3, 2018, at 1:25 AM, Honnappa Nagarahalli <Honnappa.Nagarahalli@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?
> >>>
> >>> Yes, please include.
> >>
> >> I didn't realized that this is fixing the meson build.
> >> 17.11 doesn't have that.
> >>
> >> Thanks,
> >> Yongseok
> >>
> >> It has a fix for the make build as well. Does it mean, it needs to be a different patch?
> >
> > I could've applied the second hunk but actually it was one minute
> > before the release of 17.11.4. I'm sorry that I had to skip this patch for the release.
> >
> > 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. This will
> > be included in 17.11.5 (ETA is Nov).
> >
> > FYI, the most favorable way is that you send patches with '[PATCH
> > 17.11]' prefix based on the latest stable/17.11 so that it is never forgotten.
>
> One more FYI.
> Even though this was sent to stable (without dev@dpdk.org), as you
> have also sent a same patch[1] to dev@dpdk.org, this will be queued
> for next stable releases anyway once it is merged to dpdk/master.
>
> [1] https://mails.dpdk.org/archives/dev/2018-September/110713.html
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.
My apologies. I seem to have misunderstood a comment (http://mails.dpdk.org/archives/dev/2018-August/110342.html). Do we send patches to stable@dpdk.org only when the patches are backported?
next prev parent reply other threads:[~2018-09-16 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 18:32 Honnappa Nagarahalli
2018-09-02 19:30 ` Yongseok Koh
2018-09-02 19:59 ` Honnappa Nagarahalli
2018-09-02 23:59 ` Yongseok Koh
2018-09-03 8:25 ` Honnappa Nagarahalli
2018-09-04 18:41 ` Yongseok Koh
2018-09-04 18:53 ` Yongseok Koh
2018-09-16 8:15 ` Thomas Monjalon
2018-09-16 14:40 ` Honnappa Nagarahalli [this message]
2018-09-16 19:23 ` Luca Boccassi
2018-09-02 18:35 Honnappa Nagarahalli
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=AM0PR08MB366707F4FC7488D472D815B3981F0@AM0PR08MB3667.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).