Patch ordering, is deliberate. They are not dependent on each other. I'll rebase and add the new dri-devel@xxxxxxxxxxxxxxxxxxxxx when is resubmit the patches. Peter. -----Original Message----- From: Lespiau, Damien Sent: Tuesday, March 31, 2015 2:35 PM To: Daniel Vetter Cc: Antoine, Peter; intel-gfx@xxxxxxxxxxxxxxxxxxxxx Subject: Re: [PATCH] drm: Kernel Crash in drm_unlock On Tue, Mar 31, 2015 at 03:25:32PM +0200, Daniel Vetter wrote: > > --- > > drivers/gpu/drm/drm_lock.c | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/drivers/gpu/drm/drm_lock.c b/drivers/gpu/drm/drm_lock.c > > index f645268..80253a7 100644 > > --- a/drivers/gpu/drm/drm_lock.c > > +++ b/drivers/gpu/drm/drm_lock.c > > @@ -156,6 +156,14 @@ int drm_unlock(struct drm_device *dev, void > > *data, struct drm_file *file_priv) > > Also please rebase to latest upstream when submitting patches to the > public (the function is now called drm_legacy_unlock). While we're at it, how did you send those emails to not have the patch ordering in the tags? we should have had 1/3, 2/3 and 3/3 tags there. The usual way is to give the revision of the start of the series (the patch just before what you want to send, ie. git send-email --to=intel-gfx HEAD~3 or git send-email --to=intel-gfx drm-intel/drm-intel-nightly Remember to use --dry-run the first few times if you're not sure. HTH, -- Damien --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
