[PULL] drm-intel-next

Rodrigo Vivi rodrigo.vivi at intel.com
Fri Aug 23 16:12:29 UTC 2019


On Fri, Aug 23, 2019 at 02:23:41PM +0300, Arkadiusz Hiler wrote:
> On Fri, Aug 23, 2019 at 08:46:48PM +1000, Dave Airlie wrote:
> > On Fri, 23 Aug 2019 at 20:08, Arkadiusz Hiler <arkadiusz.hiler at intel.com> wrote:
> > >
> > > On Fri, Aug 23, 2019 at 11:50:06AM +1000, Dave Airlie wrote:
> > > > On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi <rodrigo.vivi at intel.com> wrote:
> > > > >
> > > > > Hi Dave and Daniel,
> > > > >
> > > > > Here goes the final pull request targeting 5.4.
> > > >
> > > > For some reason patchwork hasn't picked this up. or if it has I can't
> > > > see it. Not sure whether it was the earlier patch code in it or
> > > > something else malformed.
> > > >
> > > > Dave.
> > >
> > > Hey,
> > >
> > > FDO's Patchwork maintainer here. Feel free to CC me if something like
> > > this happens ever again.
> > >
> > > Seems like the emails was picked up by the patchwork:
> > > https://patchwork.freedesktop.org/patch/325996/
> > >
> > > It appears as a weird mix between a pull request and a regular patch
> > > because of the in-line quoted commit from Stephen. Patchwork doesn't
> > > really know what to do in similar situations.
> > >
> > > Dave, how do you exactly check for new pull requests? I would like to
> > > know which API endpoints/interfaces I should look at. Knowing the
> > > expectations of your tooling would also help.
> > >
> > > There is probably some codepath that just doesn't work right for those
> > > dual-type patches.
> > 
> > I actually should have thought to search a bit deeper for it! I think
> > we've had this happen once before.
> > 
> > I normally just do a search for the keyword pull in the all the patches.
> > https://patchwork.freedesktop.org/project/dri-devel/patches/?submitter=&state=&q=pull&archive=&delegate=
> 
> Interesting, the original pull as well as the v2 are there now:
> https://hiler.eu/i/fd0401b0.png
> 
> Also the API endpoint seems to show them just fine:
> https://patchwork.freedesktop.org/api/1.0/projects/dri-devel/events/?name=pull-request-new :
> 	{
> 	    "name": "pull-request-new",
> 	    "event_time": "2019-08-23T08:12:37.601125",
> 	    "patch": 325996,
> 	    "parameters": {
> 		"pull_url": "git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2019-08-22"
> 	    }
> 	},
> 	{
> 	    "name": "pull-request-new",
> 	    "event_time": "2019-08-23T08:08:00.066068",
> 	    "patch": 325993,
> 	    "parameters": {
> 		"pull_url": "git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2019-08-22"
> 	    }
> 	}
> 
> FDO's mailing lists had some issues yesteday, I have got few of those
> for the e-mails that I have tried to send:
> 
> 	This is an automatically generated Delivery Status Notification.
> 	THIS IS A WARNING MESSAGE ONLY.
> 	YOU DO NOT NEED TO RESEND YOUR MESSAGE.
> 
> 	Delivery to the following recipients has been delayed.
> 	      <igt-dev at lists.freedesktop.org>
> 
> 	The reason for the problem:
> 	4.4.2 - Bad connection 'timeout'
> 
> 
> My current guess is that people who were CCed on the pull request got
> the email, checked Patchwork and it wasn't there due to the delivery
> issues.
> 
> In the v2 Rodrigo mentions:
> > for some reason my dim didn't recognized the path apparently
> 
> Rodrigo, can you elaborate? I may be missing/misunderstanding something.

Nevermind. I thought the problem was on my system when generating the
pull since I had seen a git error for being out of the tree.

The second one I generated from inside dinq directory and got it
clean.

So, in summary where are we now here? Do I need to take any action
to help this to get through?

> 
> -- 
> Cheers,
> Arek


More information about the dim-tools mailing list