public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v3 1/1] gitlab-ci: add build and tests for MIPS
Date: Thu, 27 Jun 2019 14:53:16 +0000	[thread overview]
Message-ID: <41bace6d1e9d922492da0fc7822252541ceaac96.camel@intel.com> (raw)
In-Reply-To: <20190627131916.fpakdc3wzybfpwew@ahiler-desk1.fi.intel.com>

On Thu, 2019-06-27 at 16:19 +0300, Arkadiusz Hiler wrote:
> On Thu, Jun 27, 2019 at 04:14:53PM +0300, Ser, Simon wrote:
> > On Thu, 2019-06-27 at 11:02 +0100, Guillaume Tucker wrote:
> > > On 27/06/2019 08:02, Ser, Simon wrote:
> > > > On Tue, 2019-06-25 at 14:08 +0100, Guillaume Tucker wrote:
> > > > > On 18/06/2019 13:42, Guillaume Tucker wrote:
> > > > > > Add Docker image and Gitlab CI steps to run builds and tests for
> > > > > > the
> > > > > > MIPS architecture using Debian Stretch with backports.
> > > > > > 
> > > > > > Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> > > > > > ---
> > > > > > 
> > > > > > Notes:
> > > > > >     v2: use stretch-backports and require libatomic1
> > > > > >     v3: add mips ci tests and require Debian libatomic1 for mips
> > > > > 
> > > > > The series to use portable atomics functions was merged today, so
> > > > > I think this one should now be good to go as well.  It applies
> > > > > cleanly on top of the current master branch and the Gitlab CI
> > > > > pipeline passed:
> > > > > 
> > > > >   
> > > > > https://gitlab.freedesktop.org/gtucker/igt-gpu-tools/pipelines/44704
> > > > > 
> > > > > Please let me know if you want me to resubmit it to get another
> > > > > Patchwork CI run or if anything else needs to be done.
> > > > 
> > > > LGTM!
> > > > 
> > > > Reviewed-by: Simon Ser <simon.ser@intel.com>
> > > > 
> > > > And pushed:
> > > > 
> > > > To gitlab.freedesktop.org:drm/igt-gpu-tools.git
> > > >    15ad66453441..439a9f5d615f  master -> master
> > > 
> > > Thanks!
> > > 
> > > Err, however it looks like you pushed the v2 which had only
> > > builds rather than this v3 which does builds and tests:
> > > 
> > >   439a9f5d615f gitlab-ci: add build for MIPS
> > > 
> > > I've made another patch with the difference between v2 and v3 and
> > > pushed it to my branch:
> > > 
> > >   https://gitlab.freedesktop.org/gtucker/igt-gpu-tools/commit/9693e28871f27efb7340ad29d54de4be7b5461a9
> > > 
> > > I'll wait for the Gitlab CI pipeline to complete and then I guess
> > > I should send that to the mailing list.
> > 
> > Bleh, I'm sorry about this! It seems like patchwork got confused.
> > 
> > I'll gladly review and merge a fix, feel free to Cc me :)
> 
> The title of the first patch has changed, so patchwork treats it as a
> separate series instead of a revision to existing one.
> 
> It's safer to take the patchwork links (both to series and the mbox)
> from the CI results instead of trying to browse for them yourself.

Yeah, this makes sense. Thanks for the info!
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-06-27 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 12:42 [igt-dev] [PATCH i-g-t v3 1/1] gitlab-ci: add build and tests for MIPS Guillaume Tucker
2019-06-18 13:33 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v3,1/1] " Patchwork
2019-06-19  1:18 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-06-25 13:08 ` [Intel-gfx] [PATCH i-g-t v3 1/1] " Guillaume Tucker
2019-06-27  7:02   ` [igt-dev] " Ser, Simon
2019-06-27 10:02     ` Guillaume Tucker
2019-06-27 13:14       ` Ser, Simon
2019-06-27 13:19         ` [Intel-gfx] " Arkadiusz Hiler
2019-06-27 14:53           ` Ser, Simon [this message]

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=41bace6d1e9d922492da0fc7822252541ceaac96.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=petri.latvala@intel.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