All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: greenfoo@gluegarage.com,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <sean@poorly.run>, Dave Airlie <airlied@linux.ie>,
	Jonathan Corbet <corbet@lwn.net>,
	Alexey Brodkin <abrodkin@synopsys.com>,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Archit Taneja <architt@codeaurora.org>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Russell King <linux+etnaviv@armlinux.org.uk>,
	Christian Gmeiner <christian.gmeiner@gmail.com>,
	Marek Vasut <marex@denx.de>, Stefan Agner <stefan@agner.ch>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Gilles Muller <Gilles.Muller@lip6.fr>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Michal Marek <michal.lkml@markovi.net>,
	Haneen Mohammed <hamohammed.sa@gmail.com>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"open list:VIRTIO CORE,
	NET..."  <virtualization@lists.linux-foundation.org>,
	etnaviv@lists.freedesktop.org,
	"open list:DRM DRIVERS FOR RENESAS" 
	<linux-renesas-soc@vger.kernel.org>,
	cocci@systeme.lip6.fr
Subject: Re: [PATCH 0/9] drm: remove deprecated functions
Date: Thu, 29 Nov 2018 15:55:28 +0100	[thread overview]
Message-ID: <CAKMK7uF9Q-LySAXg=kT9B-ueFR9qhr_B0N3y1g1D_OTc-+Vbdg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYmBSVKBvu=YOV87zWK8WCC+pcn9ux_W4VEYwzRzexQ_A@mail.gmail.com>

On Thu, Nov 29, 2018 at 3:45 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Mon, Nov 26, 2018 at 3:12 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Sat, Nov 24, 2018 at 10:17:13PM +0100, Linus Walleij wrote:
>
> > > It was especially scary.
> > >
> > > But I think I managed to apply the patches and push the
> > > branch now.
> >
> > Except when you're racing with someone else you should only see conflicts
> > with stuff you've just pushed. Or if someone forgot to fix up their mess.
> > What was the conflict?
>
> dim push-branches was complaining that one of the commits was
> missing the proper committer sign-off, it was the bottom commit under
> mine (IIRC "drm/atomic-helper: WARN if fake_commit->hw_done is not
> completed as expected")
> and dim update-branches seemed to rebase and fix up my patches
> and then everything was fine.

This sounds like you (or dim?) accidentaly amended that commit (which
changes the committer and results in the warning), and a rebase would
indeed have fixed that. If the first patch conflicts this can happen
because dim apply-branch doesn't bail out correctly. Or at least did
in the past, I recently fixed that in

commit ee299e510ae468aab27610bcbc4fdd4de932f74b
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed Oct 17 08:53:00 2018 +0200

    dim: make apply-patch fail again

> I just felt slightly out of control :D

If your dim didn't have the above commit and you had a conflict it's
all explained. Otherwise I'm not sure what's been going on ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Haneen Mohammed <hamohammed.sa@gmail.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Gilles Muller <Gilles.Muller@lip6.fr>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	cocci@systeme.lip6.fr, Marek Vasut <marex@denx.de>,
	Archit Taneja <architt@codeaurora.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Alexey Brodkin <abrodkin@synopsys.com>,
	Dave Airlie <airlied@linux.ie>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	greenfoo@gluegarage.com,
	Russell King <linux+etnaviv@armlinux.org.uk>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	etnaviv@lists.freedesktop.org,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Christian Gmeiner <christian.gmeiner@gmail.com>,
	Stefan Agner <stefan@agner.ch>,
	"open list:VIRTIO CORE,
	NET..." <virtualization@lists.linux-foundation.org>,
	Sean Paul <sean@poorly.run>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	"open list:DRM DRIVERS FOR RENESAS"
	<linux-renesas-soc@vger.kernel.org>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH 0/9] drm: remove deprecated functions
Date: Thu, 29 Nov 2018 15:55:28 +0100	[thread overview]
Message-ID: <CAKMK7uF9Q-LySAXg=kT9B-ueFR9qhr_B0N3y1g1D_OTc-+Vbdg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYmBSVKBvu=YOV87zWK8WCC+pcn9ux_W4VEYwzRzexQ_A@mail.gmail.com>

On Thu, Nov 29, 2018 at 3:45 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Mon, Nov 26, 2018 at 3:12 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Sat, Nov 24, 2018 at 10:17:13PM +0100, Linus Walleij wrote:
>
> > > It was especially scary.
> > >
> > > But I think I managed to apply the patches and push the
> > > branch now.
> >
> > Except when you're racing with someone else you should only see conflicts
> > with stuff you've just pushed. Or if someone forgot to fix up their mess.
> > What was the conflict?
>
> dim push-branches was complaining that one of the commits was
> missing the proper committer sign-off, it was the bottom commit under
> mine (IIRC "drm/atomic-helper: WARN if fake_commit->hw_done is not
> completed as expected")
> and dim update-branches seemed to rebase and fix up my patches
> and then everything was fine.

This sounds like you (or dim?) accidentaly amended that commit (which
changes the committer and results in the warning), and a rebase would
indeed have fixed that. If the first patch conflicts this can happen
because dim apply-branch doesn't bail out correctly. Or at least did
in the past, I recently fixed that in

commit ee299e510ae468aab27610bcbc4fdd4de932f74b
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed Oct 17 08:53:00 2018 +0200

    dim: make apply-patch fail again

> I just felt slightly out of control :D

If your dim didn't have the above commit and you had a conflict it's
all explained. Otherwise I'm not sure what's been going on ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: greenfoo@gluegarage.com,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <sean@poorly.run>, Dave Airlie <airlied@linux.ie>,
	Jonathan Corbet <corbet@lwn.net>,
	Alexey Brodkin <abrodkin@synopsys.com>,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Archit Taneja <architt@codeaurora.org>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Russell King <linux+etnaviv@armlinux.org.uk>,
	Christian
Subject: Re: [PATCH 0/9] drm: remove deprecated functions
Date: Thu, 29 Nov 2018 15:55:28 +0100	[thread overview]
Message-ID: <CAKMK7uF9Q-LySAXg=kT9B-ueFR9qhr_B0N3y1g1D_OTc-+Vbdg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYmBSVKBvu=YOV87zWK8WCC+pcn9ux_W4VEYwzRzexQ_A@mail.gmail.com>

On Thu, Nov 29, 2018 at 3:45 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Mon, Nov 26, 2018 at 3:12 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Sat, Nov 24, 2018 at 10:17:13PM +0100, Linus Walleij wrote:
>
> > > It was especially scary.
> > >
> > > But I think I managed to apply the patches and push the
> > > branch now.
> >
> > Except when you're racing with someone else you should only see conflicts
> > with stuff you've just pushed. Or if someone forgot to fix up their mess.
> > What was the conflict?
>
> dim push-branches was complaining that one of the commits was
> missing the proper committer sign-off, it was the bottom commit under
> mine (IIRC "drm/atomic-helper: WARN if fake_commit->hw_done is not
> completed as expected")
> and dim update-branches seemed to rebase and fix up my patches
> and then everything was fine.

This sounds like you (or dim?) accidentaly amended that commit (which
changes the committer and results in the warning), and a rebase would
indeed have fixed that. If the first patch conflicts this can happen
because dim apply-branch doesn't bail out correctly. Or at least did
in the past, I recently fixed that in

commit ee299e510ae468aab27610bcbc4fdd4de932f74b
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed Oct 17 08:53:00 2018 +0200

    dim: make apply-patch fail again

> I just felt slightly out of control :D

If your dim didn't have the above commit and you had a conflict it's
all explained. Otherwise I'm not sure what's been going on ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  parent reply	other threads:[~2018-11-29 14:55 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 22:16 [PATCH 0/9] drm: remove deprecated functions Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` [PATCH 1/9] drm: replace "drm_gem_object_unreference_unlocked" function with "*put_unlocked" Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-24 20:38   ` Linus Walleij
2018-11-24 20:38     ` Linus Walleij
2018-11-24 20:38     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 2/9] drm: remove deprecated "[__]drm_gem_object_[un]reference[_locked]" functions Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-24 20:38   ` Linus Walleij
2018-11-24 20:38     ` Linus Walleij
2018-11-24 20:38     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put" Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 23:00   ` Boris Brezillon
2018-11-15 23:00     ` Boris Brezillon
2018-11-15 23:00     ` Boris Brezillon
2018-11-16 10:15   ` Lucas Stach
2018-11-16 10:15     ` Lucas Stach
2018-11-16 10:15     ` Lucas Stach
2018-11-16 17:04     ` Fernando
2018-11-16 17:04       ` Fernando
2018-11-16 17:04       ` Fernando
2018-11-20  9:53       ` Jani Nikula
2018-11-20  9:53       ` Jani Nikula
2018-11-20  9:53         ` Jani Nikula
2018-11-20  9:53         ` Jani Nikula
2018-11-24 20:44       ` Linus Walleij
2018-11-24 20:44         ` Linus Walleij
2018-11-24 20:44         ` Linus Walleij
2018-11-16 11:41   ` Alexey Brodkin
2018-11-16 11:41     ` Alexey Brodkin
2018-11-16 11:41     ` Alexey Brodkin
2018-11-19 11:39   ` Stefan Agner
2018-11-19 11:39     ` Stefan Agner
2018-11-19 11:39     ` Stefan Agner
2018-11-19 12:13   ` Shawn Guo
2018-11-19 12:13     ` Shawn Guo
2018-11-19 12:13     ` Shawn Guo
2018-11-19 12:13   ` Shawn Guo
2018-11-24 20:44   ` Linus Walleij
2018-11-24 20:44     ` Linus Walleij
2018-11-24 20:44     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 4/9] drm: remove deprecated "drm_dev_unref" function Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-24 20:45   ` Linus Walleij
2018-11-24 20:45     ` Linus Walleij
2018-11-24 20:45     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 5/9] drm: replace "drm_connector_unreference" with "drm_connector_put" Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-24 20:47   ` Linus Walleij
2018-11-24 20:47     ` Linus Walleij
2018-11-24 20:47     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 6/9] drm: remove deprecated "drm_connector_[un]reference" functions Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-21 18:56   ` Lyude Paul
2018-11-21 18:56     ` Lyude Paul
2018-11-21 18:56     ` Lyude Paul
2018-11-24 20:49   ` Linus Walleij
2018-11-24 20:49     ` Linus Walleij
2018-11-24 20:49     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 7/9] drm: remove deprecated "drm_framebuffer_[un]reference" functions Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-24 20:55   ` Linus Walleij
2018-11-24 20:55     ` Linus Walleij
2018-11-24 20:55     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 8/9] drm: remove no longer needed drm-get-put coccinelle script Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-18 11:04   ` Julia Lawall
2018-11-18 11:04   ` Julia Lawall
2018-11-18 11:04     ` Julia Lawall
2018-11-18 11:04     ` Julia Lawall
2018-11-24 20:58   ` Linus Walleij
2018-11-24 20:58     ` Linus Walleij
2018-11-24 20:58     ` Linus Walleij
2018-11-15 22:16 ` [PATCH 9/9] docs: drm: remove no longer relevant TODO entry Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-15 22:16   ` Fernando Ramos
2018-11-24 20:59   ` Linus Walleij
2018-11-24 20:59     ` Linus Walleij
2018-11-24 20:59     ` Linus Walleij
2018-11-15 22:38 ` [PATCH 0/9] drm: remove deprecated functions Linus Walleij
2018-11-15 22:38   ` Linus Walleij
2018-11-15 22:38   ` Linus Walleij
2018-11-21  9:42   ` Daniel Vetter
2018-11-21  9:42   ` Daniel Vetter
2018-11-21  9:42     ` Daniel Vetter
2018-11-21  9:42     ` Daniel Vetter
2018-11-21 18:21     ` Laurent Pinchart
2018-11-21 18:21     ` Laurent Pinchart
2018-11-22  8:55       ` Daniel Vetter
2018-11-22  8:55       ` Daniel Vetter
2018-11-22  8:55         ` Daniel Vetter
2018-11-22  8:55         ` Daniel Vetter
2018-11-24 21:17     ` Linus Walleij
2018-11-24 21:17       ` Linus Walleij
2018-11-24 21:17       ` Linus Walleij
2018-11-26 14:12       ` Daniel Vetter
2018-11-26 14:12         ` Daniel Vetter
2018-11-26 14:12         ` Daniel Vetter
2018-11-29 14:45         ` Linus Walleij
2018-11-29 14:45           ` Linus Walleij
2018-11-29 14:55           ` Daniel Vetter
2018-11-29 14:55           ` Daniel Vetter [this message]
2018-11-29 14:55             ` Daniel Vetter
2018-11-29 14:55             ` Daniel Vetter
2018-11-29 14:55             ` Daniel Vetter
2018-11-26 14:12       ` Daniel Vetter

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='CAKMK7uF9Q-LySAXg=kT9B-ueFR9qhr_B0N3y1g1D_OTc-+Vbdg@mail.gmail.com' \
    --to=daniel@ffwll.ch \
    --cc=Gilles.Muller@lip6.fr \
    --cc=Julia.Lawall@lip6.fr \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=abrodkin@synopsys.com \
    --cc=airlied@linux.ie \
    --cc=alexandre.belloni@bootlin.com \
    --cc=architt@codeaurora.org \
    --cc=boris.brezillon@bootlin.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=greenfoo@gluegarage.com \
    --cc=hamohammed.sa@gmail.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kraxel@redhat.com \
    --cc=l.stach@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux+etnaviv@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marex@denx.de \
    --cc=maxime.ripard@bootlin.com \
    --cc=michal.lkml@markovi.net \
    --cc=nicolas.ferre@microchip.com \
    --cc=nicolas.palix@imag.fr \
    --cc=sean@poorly.run \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=virtualization@lists.linux-foundation.org \
    /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.