From: Thomas Monjalon <thomas@monjalon.net>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dev@dpdk.org, Luca Boccassi <bluca@debian.org>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v3] build: establish an invariant machine type
Date: Sun, 18 Nov 2018 14:24:04 +0100 [thread overview]
Message-ID: <2310639.fA7hNCVAbZ@xps> (raw)
In-Reply-To: <CAATJJ0JD_5UnBERw_PjYFKHjCGhWF+4-1gDa8e2xDvjY+mVSAQ@mail.gmail.com>
14/11/2018 20:39, Christian Ehrhardt:
> On Wed, Nov 14, 2018 at 3:33 PM Christian Ehrhardt
> <christian.ehrhardt@canonical.com> wrote:
> >
> > Add the machine definition 'default' which is special compared
> > to 'native' (most optimized for current system) or any explicit
> > type (external entity has to decide on the type).
> >
> > It defaults to the per arch agreed common minimal baseline
> > needed for DPDK to reasonable work.
> >
> > That might not be the most optimized, but the most portable
> > version while still being able to support the CPU features
> > required for DPDK.
> >
> > Going forward this can be bumped up by the DPDK project, but it
> > can never be an invariant like 'native'.
> >
> > Distributions and other needing portable code are expected to
> > define the machine as 'default'.
> >
> > Changes in v2:
> > - fixed the non 64 bit arm default type
> > - changed baseline to default to match the old build system
> >
> > Changes in v3:
> > - add acked-by's
> > - removed old wording from commit message
> > - adding Fixes line per request by Luca Boccassi
>
> FYI: I'll drop the version update from the commit (I didn't have a
> cover letter to add them instead).
You don't need a cover letter for changelogs.
You can insert it after ---
Usually, I insert changelogs between two --- lines.
next prev parent reply other threads:[~2018-11-18 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 11:34 [PATCH 1/2] build: avoid non supported -march on ppc (meson) Christian Ehrhardt
2018-11-14 11:34 ` [PATCH 2/2] build: establish an invariant machine type Christian Ehrhardt
2018-11-14 11:40 ` Luca Boccassi
2018-11-14 11:52 ` Bruce Richardson
2018-11-14 12:05 ` Luca Boccassi
2018-11-14 13:09 ` Christian Ehrhardt
2018-11-14 13:18 ` [PATCH] " Christian Ehrhardt
2018-11-14 13:54 ` Bruce Richardson
2018-11-14 14:33 ` [PATCH v3] " Christian Ehrhardt
2018-11-14 19:39 ` Christian Ehrhardt
2018-11-18 13:24 ` Thomas Monjalon [this message]
2018-11-14 19:40 ` [PATCH v4 1/2] build: avoid non supported -march on ppc (meson) Christian Ehrhardt
2018-11-14 19:40 ` [PATCH v4 2/2] build: establish an invariant machine type Christian Ehrhardt
2018-11-18 14:24 ` [PATCH v4 1/2] build: avoid non supported -march on ppc (meson) Thomas Monjalon
2018-11-14 13:06 ` [PATCH 2/2] build: establish an invariant machine type Luca Boccassi
2018-11-14 13:08 ` Christian Ehrhardt
2018-11-14 11:39 ` [PATCH 1/2] build: avoid non supported -march on ppc (meson) Luca Boccassi
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=2310639.fA7hNCVAbZ@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.