DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Aaron Conole <aconole@redhat.com>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Juraj Linkeš <juraj.linkes@pantheon.tech>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"maicolgabriel@hotmail.com" <maicolgabriel@hotmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>
Subject: Re: [dpdk-dev] [RFC PATCH v1 0/2] Travis CI jobs update after credits
Date: Wed, 17 Feb 2021 16:08:25 +0000
Message-ID: <DBAPR08MB58146FC37AAA3188D84752B498869@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <f7tczwy8zo9.fsf@dhcp-25.97.bos.redhat.com>

<snip>

> Subject: Re: [dpdk-dev] [RFC PATCH v1 0/2] Travis CI jobs update after
> credits
> 
> Ferruh Yigit <ferruh.yigit@intel.com> writes:
> 
> > On 2/17/2021 9:42 AM, Juraj Linkeš wrote:
> >> Since Travis added credits we need to make some changes to the Travis
> >> CI. Arm has a credit agreement with Travis for arm jobs, so remove
> >> x86 jobs. Also, migrate all arm jobs to the latest environment.
> >>
> >
> > So this is becoming supporting a CI infrastructure within DPDK for a
> > specific vendor, do we want this?
> >
> > And can't this Travis credit/support be expanded for the whole
> > project, so everyone in the community benefit from it?
> 
> I agree - it would be best to have it working universally.
My understanding is that the credits are not associated with any architecture.

> 
> >> Juraj Linkeš (2):
> >>    ci: remove x86 Travis jobs
> >>    ci: update arm64 Travis jobs to Graviton2
> >>
> >>   .travis.yml | 113 ++++++++--------------------------------------------
> >>   1 file changed, 16 insertions(+), 97 deletions(-)
> >>


  reply	other threads:[~2021-02-17 16:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  9:42 Juraj Linkeš
2021-02-17  9:42 ` [dpdk-dev] [RFC PATCH v1 1/2] ci: remove x86 Travis jobs Juraj Linkeš
2021-02-17 10:39   ` Thomas Monjalon
2021-02-17 15:44     ` Aaron Conole
2021-02-17 17:18       ` Honnappa Nagarahalli
2021-02-17 15:47   ` Aaron Conole
2021-02-17 17:19     ` Honnappa Nagarahalli
2021-02-17  9:42 ` [dpdk-dev] [RFC PATCH v1 2/2] ci: update arm64 Travis jobs to Graviton2 Juraj Linkeš
2021-02-17 10:43 ` [dpdk-dev] [RFC PATCH v1 0/2] Travis CI jobs update after credits Ferruh Yigit
2021-02-17 15:46   ` Aaron Conole
2021-02-17 16:08     ` Honnappa Nagarahalli [this message]
2021-02-18  2:40 ` Honnappa Nagarahalli
2021-02-18  7:50   ` Juraj Linkeš
2021-02-19  7:34 ` [dpdk-dev] [PATCH v2] ci: update arm64 Travis jobs to Graviton2 Juraj Linkeš
2021-02-19  9:13   ` Ruifeng Wang
2021-02-19 13:27   ` Aaron Conole
2021-02-22 14:49     ` Juraj Linkeš
2021-02-22 19:37       ` Aaron Conole
2021-02-23  8:28   ` [dpdk-dev] [PATCH v3] " Juraj Linkeš
2021-02-23  9:02     ` Ruifeng Wang
2021-02-23 14:38     ` Aaron Conole
2021-03-02 12:39     ` David Marchand

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=DBAPR08MB58146FC37AAA3188D84752B498869@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=maicolgabriel@hotmail.com \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git