Re: [PATCH 2/5] dim: auto-commit in apply-pull if rerere solved it all

On 5 May 2018 at 00:10, Jani Nikula wrote: > On Fri, 04 May 2018, Daniel Vetter wrote: >> Now that we experiment with dim for drm-next it's much more likely >> that pull requests have conflicts. But also that dim already knows >> about them,

Re: [PATCH] dim: switch to dry-run in warn_or_fail

Yeah this seems useful after doing my first -f pull today. Acked-by: Dave Airlie <airl...@redhat.com> On 4 May 2018 at 15:21, Daniel Vetter <daniel.vet...@ffwll.ch> wrote: > When merging a pull requests there's potentially a long list of > problematic patches. By switching to d

Re: current dim master misapplies a pull

On 14 May 2018 at 16:13, Daniel Vetter <dan...@ffwll.ch> wrote: > On Mon, May 14, 2018 at 7:18 AM, Dave Airlie <airl...@gmail.com> wrote: >> Trying to apply: >> https://patchwork.freedesktop.org/patch/221740/ >> >> It fails with missing link, it appears to

current dim master misapplies a pull

Trying to apply: https://patchwork.freedesktop.org/patch/221740/ It fails with missing link, it appears to git amend the last commit in my tree with the link. Dave. ___ dim-tools mailing list dim-tools@lists.freedesktop.org

Re: [PULL] drm-misc-next

On 26 April 2018 at 20:53, Maarten Lankhorst wrote: > Hi Dave, > > This is my first pull request for v4.18. Only UAPI change is adding a generic > plane > alpha property, which replaces the driver specific ones in sun4i, rcar-du and > atmel-hclcdc. > > drm-misc-next-2018-04-26: > drm-misc-next

[PATCH] [rfc/not done right] hack to generate pull request

I wanted to avoid the mutt bit, and dump it to a file so I can scp it to somewhere else. --- dim | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/dim b/dim index e477d043458b..c2d377dd9694 100755 --- a/dim +++ b/dim @@ -1896,6 +1896,9 @@ function

[PATCH] [rfc/not done right] hack to generate pull request

From: Dave Airlie I wanted to avoid the mutt bit, and dump it to a file so I can scp it to somewhere else. --- dim | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/dim b/dim index e477d043458b..c2d377dd9694 100755 --- a/dim +++ b/dim @@ -1896,6 +1896,9

Re: dim apply-pull doesn't work for Maarten's last drm-misc pull

On 30 April 2018 at 09:22, Dave Airlie <airl...@gmail.com> wrote: > I'm likely doing it wrong, but I took the pull from gmail and saved > it, please find the saved txt attached, > then I ran > > cat /tmp/pullreq.txt | dim apply-patch drm-next Doh looks like Ctrl-Ms th

dim apply-pull doesn't work for Maarten's last drm-misc pull

le.com: best guess record for domain of maar...@mblankhorst.nl designates 2a02:2308::216:3eff:fe92:dfa3 as permitted sender) smtp.mailfrom=maar...@mblankhorst.nl To: Dave Airlie <airl...@gmail.com> Cc: Daniel Vetter <daniel.vet...@ffwll.ch>, Jani Nikula <jani.nik...@linux.intel.c

Re: [PULL] drm-intel-next

On 4 May 2018 at 10:29, Dave Airlie <airl...@gmail.com> wrote: > On 4 May 2018 at 10:19, Dave Airlie <airl...@gmail.com> wrote: >> On 2 May 2018 at 17:03, Jani Nikula <jani.nik...@intel.com> wrote: >>> >>> Hi Dave - >>> >>> drm-

Re: [PATCH] dim: allow tags in backmerges

t of the window > unfortunately. > > v2: Unlazy and also update the docs. > > v3: Make the check work from anywhere, we need to move the cd a bit > up (Dave). Tested-by: Dave Airlie Reviewed-by: Dave Airlie > > Requested-by: Dave Airlie > Cc: Dave Airlie > Signe

Re: [PULL] drm-intel-next

On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > First batch of features for 5.2, tagged last week. I asked on irc, but got no answer I saw, /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/i915_gem_context.c:698:12: warning: ‘context_barrier_task’ defined

Re: [PULL] drm-intel-next

On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > Here goes another pull request for 5.1. dim complained: Chris committed this without an S-O-B, now because it's all Intel this probably doesn't matter, so I'll pull it, put please try and let it not happen again.

Re: [PULL] drm-intel-next

On Fri, 23 Aug 2019 at 20:08, Arkadiusz Hiler wrote: > > On Fri, Aug 23, 2019 at 11:50:06AM +1000, Dave Airlie wrote: > > On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi wrote: > > > > > > Hi Dave and Daniel, > > > > > > Here goes the final pul

Re: [PULL] drm-intel-next

On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi 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.

Re: [PULL] drm-misc-next

On Sat, 3 Aug 2019 at 20:47, Maxime Ripard wrote: > > Hi Daniel, Dave, > > Here is the first (and pretty late) drm-misc-next PR. > > It's pretty big due to the lateness, but there's nothing really major > showing up. It's pretty much the usual bunch of reworks, fixes, and > new helpers being

Re: [Intel-gfx] [PULL] drm-misc-next

On Tue, 22 Oct 2019 at 01:49, Sean Paul wrote: > > On Mon, Oct 21, 2019 at 4:11 AM Tomi Valkeinen wrote: > > > > Hi, > > > > On 18/10/2019 23:11, Sean Paul wrote: > > > On Fri, Oct 18, 2019 at 9:46 AM Tomi Valkeinen > > > wrote: > > >> > > >> Hi Sean, > > >> > > >> On 17/10/2019 22:26, Sean

Re: [PATCH] dim: don't choke on quoted pull requests

Seems like a good plan. Acked-by: Dave Airlie On Wed, 18 Dec 2019 at 22:08, Daniel Vetter wrote: > > Maintainers seem to like to supply fixed up pull requests in replies > to their previous attempt. Current dim then choked on that pile, > trying to pull the old one (but get

Re: [PULL] drm-intel-next

On Thu, 14 May 2020 at 03:10, Joonas Lahtinen wrote: > > Ping for merging this? If there are no issues, I'd prefer to pull in > next gvt-next and tag the final pull sooner than later. Can you check that I'm correct and this isn;'t in patchwork. I've checked both the dri-devel and intel-gfx

Re: [PULL] drm-intel-next-fixes

On Fri, 31 Jul 2020 at 02:26, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > (Covering for Jani here for drm-intel-next-fixes) > > 5 new commits over drm-intel-next here. > > Fix for KASAN detected race condition and linux-next scheduler > WARNs. Patch to avoid IRQ spinlock and Cc: stable PMU

Re: [PATCH] dim: Fix maintainer-tools setup

m gitlab raw. Dave. > > BR, > Jani. > > > > > > > Reported-by: Dave Airlie > > Cc: Dave Airlie > > Signed-off-by: Daniel Vetter > > --- > > dim | 8 ++-- > > 1 file changed, 6 insertions(+), 2 deletions(-) > > > > d

Re: [PATCH] dim: Fix maintainer-tools setup

On Wed, 5 Aug 2020 at 17:04, Daniel Vetter wrote: > > Setup instructions don't match the code anymore, ever since the split > to a separate repo we don't set it up automatically anymore. Readd > that - the right link and all was already there. > > Reported-by: Dave Airlie

Re: [PULL] drm-intel-fixes

On Fri, 13 Nov 2020 at 09:08, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > This is the same set as last week + couple new fixes targeting stable. > But I merged last weeks set and it's in rc3, maybe you can generate the pull request relative to origin/master or drm/drm-fixes because I'm not

Re: [PATCH] dim: decode email message content charset to unicode

is this why I get dim apply-pull drm-next < /tmp/PULL-drm-intel-next-queued.patch Traceback (most recent call last): File "", line 9, in File "", line 7, in print_msg UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 1256: ordinal not in range(128) now? just

Re: [PULL] drm-misc-next-fixes

On Fri, 18 Jun 2021 at 12:26, Dave Airlie wrote: > > when I pulled this in drm-next I got these. > > were the mst fixes meant for next or fixes btw? I'm not really sure, > but either way I don't think this is a local reason it doesn't build > or did I miss something? Hi Thom

Re: [PULL] drm-intel-gt-next

On Wed, 2 Jun 2021 at 10:28, Dave Airlie wrote: > > This has these two patches applied, and it doesn't build. > > drm/i915: drop the __i915_active_call pointer packing > drm/i915: Fix crash in auto_retire > > The latter patch shouldn't be necessary after the former,

Re: [PULL] drm-intel-gt-next

This has these two patches applied, and it doesn't build. drm/i915: drop the __i915_active_call pointer packing drm/i915: Fix crash in auto_retire The latter patch shouldn't be necessary after the former, please fix that up and resend and please build test trees before I get them in future.

Re: [PULL] drm-intel-gt-next

On Wed, 2 Jun 2021 at 14:17, Dave Airlie wrote: > > On Wed, 2 Jun 2021 at 10:28, Dave Airlie wrote: > > > > This has these two patches applied, and it doesn't build. > > > > drm/i915: drop the __i915_active_call pointer packing > > drm/i915: Fix crash in

Re: [PULL] drm-intel-fixes

On Thu, 11 Mar 2021 at 21:28, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > Things are very quiet. Only 1 fix this round. > Since I will be out next week, if this trend continues I will > accumulate 2 weeks and send when in -rc4. > > Here goes drm-intel-fixes-2021-03-11: > > - Wedge the GPU if

Re: [PULL] drm-misc-fixes

On Wed, 24 Feb 2021 at 20:27, Thomas Zimmermann wrote: > > Hi Dave and Daniel, > > here's this week's PR for drm-misc-fixes. One of the patches is a memory > leak; the rest is for hardware issues. > This is based on 5.11 and I'm not currently in the market for a backmege now before rc1 so can

Re: [PULL] drm-misc-fixes

On Thu, 9 Sept 2021 at 03:44, Thomas Zimmermann wrote: > > Hi Dave and Daniel, > > here's this week's PR for drm-misc-fixes. One patch is a potential deadlock > in TTM, the other enables an additional plane in kmb. I'm slightly unhappy > that the latter one ended up in -fixes as it's not a bugfix

Re: [PULL] drm-misc-fixes

On Thu, 9 Sept 2021 at 19:30, Daniel Vetter wrote: > > On Thu, Sep 9, 2021 at 5:35 AM Dave Airlie wrote: > > > > On Thu, 9 Sept 2021 at 03:44, Thomas Zimmermann wrote: > > > > > > Hi Dave and Daniel, > > > > > > here's this week's PR for dr

Re: [PULL] drm-misc-fixes

> - Respun clock fixes for vc4/hdmi. I was uneasy with these patches due to the number and size of them at this point in the cycle. Is there any major problem leaving them until next? I think fixes needs a hard reset and rebase to rc6 when it's tagged. If these are super-urgent fixes then I'd

Re: [PULL] drm-misc-next

On Fri, 16 Jul 2021 at 21:07, Maarten Lankhorst wrote: > > Hi Dave & Daniel, > > Lots of stuff this time around. > > Enjoy! I've pulled this but there is an outstanding warning /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c: In function ‘hibmc_unload’:

Re: [PULL] drm-intel-gt-next

On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > Here is the first drm-intel-gt-next feature PR towards v5.18. Am I missing some previous drm-intel pull? /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/gt/intel_workarounds.c: In function

Re: [PULL] drm-intel-gt-next

On Mon, 31 Oct 2022 at 21:07, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > Here goes first drm-intel-gt-next pull req towards 6.2. > > We have a fix for #6222 (kernel memory corruption issue) and fix for > display regression after resume. A missing W/A for Gen12 iGPUs and > extension of

Re: [PULL] drm-intel-gt-next

On Thu, 15 Feb 2024 at 20:06, Tvrtko Ursulin wrote: > > Hi Dave, Daniel, > > First pull request for 6.9 with probably one more coming in one to two > weeks. > > Nothing to interesting in this one, mostly a sprinkle of small fixes in > GuC, HuC, Perf/OA, a tiny bit of prep work for future