All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Pushing commits to drm-intel-next-queued and questions about CI
Date: Tue, 07 Nov 2017 18:50:24 +0200	[thread overview]
Message-ID: <87r2taav8v.fsf@intel.com> (raw)
In-Reply-To: <ec1420a6-2b2e-dad4-ca87-35b7f9712d2e@redhat.com>

On Tue, 07 Nov 2017, Hans de Goede <hdegoede@redhat.com> wrote:
> Hi,
>
> On 03-11-17 20:11, Hans de Goede wrote:
>> Hi,
>> 
>> On 03-11-17 19:51, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 03-11-17 18:40, Rodrigo Vivi wrote:
>>>> Hi Hans,
>>>>
>>>> On Fri, Nov 03, 2017 at 10:41:55AM +0000, Hans de Goede wrote:
>>>>> Hi Daniel,
>>>>>
>>>>> A while ago I was granted commit rights to the drm-intel repo.
>>>>> So far I've not used these, but since no-one seems to be
>>>>> pushing these 2 sets, I guess now might be a good time to
>>>>> learn how to push things myself.
>>>>>
>>>>> I'm talking about these 2 patch-sets:
>>>>>
>>>>> https://patchwork.freedesktop.org/series/32274/
>>>>
>>>> For this one we got the ack from Ingo, but I missed the reviewed-by
>>>> on the second one that is the i915 part of it.
>>>> Do we need it or just that ack was enough for both patches?
>>>
>>> With "this one" I assume you mean the one below:
>>>
>>>>> https://patchwork.freedesktop.org/series/32288/
>>>
>>> As that is the one which has an ack from Ingo, the second
>>> one has had a reviewed-by from Imre Deak for a few
>>> versions already, it is right there in patch work.
>>>
>>> Thank you for rescheduling the tests, this one passes
>>> Fi.CI.BAT now, but I did not see Fi.CI.IGD getting run?
>> 
>> Ok I just got a success report for Fi.CI.IGD too, so I
>> guess I can go and push this now ?
>
> Erm, ping? So given the patches have a Reviewed-by /
> Acked-by and Fi.CI.Bat and Fi.CI.IGD both pass:
>
> https://patchwork.freedesktop.org/series/32288/
>
> Can I push these (and others in similar circumstances in
> the future) ?

Yes, as long as you use dim for that [1].

BR,
Jani.


[1] https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html


>
> Regards,
>
> Hans
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-07 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 10:41 Pushing commits to drm-intel-next-queued and questions about CI Hans de Goede
2017-11-03 17:40 ` Rodrigo Vivi
2017-11-03 18:51   ` Hans de Goede
2017-11-03 19:11     ` Hans de Goede
2017-11-07 12:33       ` Hans de Goede
2017-11-07 16:50         ` Jani Nikula [this message]
2017-11-10 12:20           ` Hans de Goede

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=87r2taav8v.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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 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.